Problem with WebService MBean

[kesanenk]

I have my own MBean that is started just after when last of my ejbs is deployd (I have made dependency). Everything else work fine but WebService does not start anymore and JMX console shows only 4 registered MBeans! If I don't deploy my mbean WebService starts correcly. Starting my mbean takes about 1.5 minutes so can it cause some timeout problem?

I have also tried to make this kind of dependendy to my mbean

depends-list-element>jboss.j2ee:module=ejb-management.jar,service=EjbModule</depends-list-element>

Then everything starts fine but JMX console still finds only 4 mbeans and after a while I will get exception that StateManager is not registered while trying to use JMS. It works few minutes ok (also JMS). I am using jboss 3.2.1 and JRE 1.4.2

WebService problem:

org.jboss.util.NestedRuntimeException: Error creating MBeanProxy: jboss:service=WebService; - nested throwable: (javax.management.InstanceNotFoundException: jboss:service=WebService is not registered.)
at org.jboss.mx.util.MBeanProxyExt.(MBeanProxyExt.java:79)
at org.jboss.mx.util.MBeanProxyExt.create(MBeanProxyExt.java:283)
at org.jboss.mx.util.MBeanProxyExt.create(MBeanProxyExt.java:248)
at org.jboss.ejb.EjbModule.destroyService(EjbModule.java:359)
at org.jboss.ejb.EjbModule.createService(EjbModule.java:308)
at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:158)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

Btw. What kind of dependendy I need to define if I want my mbean to be started when everything else is up and running?

Best regards,

Kari

[juha]

What 4 MBeans do you see on the JMX console? Do you create your own instances of MBean servers?

-- Juha

[kesanenk]

I see LoaderRepository, MbeanRegistry, MBeanServerDelegate and one of my own mbeans. Actually I am creating mbean server instances. I have one mbean that extend ServiceMBeanSupport and this mbean creates instances of several other mbeans and also registers them.

- Kari

[juha]

The jmx-console is connecting to the wrong mbean server, I think this was fixed with 3.2.2RCx

-- Juha

[kesanenk]

Ok, I don't look jmx console anymore. But how about this my original problem? I don't know does this belong to here or JMS forum but anyway. Why StateManager is not registered anymore? I was thinking that there was something more wrong because jmx console has a bug but propably everythin else works fine. I will get this when trying to login new client when appserver has run couble of hours. There is not exception before this.

2003-10-01 08:25:50,825 ERROR [org.jboss.mq.sm.file.DynamicLoginModule] Failed to load DynamicSecurityManager
javax.management.InstanceNotFoundException: jboss.mq:service=StateManager is not registered.
at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:354)
at org.jboss.mx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java:445)
at org.jboss.mq.sm.file.DynamicLoginModule.initialize(DynamicLoginModule.java:53)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)


- Kari

[juha]

Try the JMS forum, I don't know the answer to this one.

-- Juha

[mpiraccini]

Did you solved this problem? We have exactly the same difficulties with a custom MBean deploy...

[juha]

If you are creating your own instances of MBean server then you need to update to 3.2.2.

If you have a JMS problem then try the JMS forum. It's not clear what is the problem you're having (as the above poster had several).

-- Juha