Help: Deploys fine under 3.0.6, but fails on jboss 3.2.0

[geirhoe]

Hi.

We are in the process of upgrading from jboss 3.0.6 to 3.2.x and are experiencing problems with our application.

During jboss startup we receive the following exception:

2003-05-15 11:02:58,332 INFO [EjbModule] Starting
2003-05-15 11:02:58,333 INFO [StatelessSessionContainer] Starting
2003-05-15 11:02:58,350 ERROR [StatelessSessionContainer] Starting failed
java.lang.RuntimeException: invoker is null: jboss:service=invoker,type=jrmp
at org.jboss.proxy.ejb.ProxyFactory.setupInvokers(ProxyFactory.java:184)
at org.jboss.proxy.ejb.ProxyFactory.start(ProxyFactory.java:171)
at org.jboss.ejb.StatelessSessionContainer.startService(StatelessSessionContainer.java:199)
at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192)
[.........]

, but if we deploy the .sar file after jboss has started the mbean deploys ok.

We have tried to add <depends>jboss:service=invoker,type=jrmp</depends> for the mbean without any success.

Thanks in advance.

Geir Inge

[adrian.brock]

InvokerProxyBinding

Look at standardjboss.xml or use search in
the forums.

Regards,
Adrian

[geirhoe]

Sorry, but your reply was a bit cryptic for me as a jboss novoise. Could you please elaborate more ? (I have tried to searching and looking at the standardjboss.xml, but need more clues).

Thanks in advance.

Geir Inge

[adrian.brock]

Looks like search is broken again. :-(

In 3.2 the invoker configuration has been
separated from the container.
You can now deploy an ejb once and attach
it to multiple invokers, e.g. http, rmi, iiop, etc.

If you look in standardjboss.xml you will
see the invoker proxy bindings and some simple
examples of linking them to the containers.

This replaces the
<container-invoker>
<client-interceptors>
of previous versions that only allowed one
protocol per container.

This explanation is probably even more cryptic :-)

Regards,
Adrian