Exception in stopping MBean Service in JBoss 4.0.5

[formica]

I have noticed a different behaviour from JBoss 4.0.4 and 4.0.5 in stopping an MBean service that I have created using annotations.

In 4.0.4 I had:

18:32:18,307 INFO [BfieldcalibrationSchedulerMBean] BfieldcalibrationScheduler has been stopped
18:32:18,311 INFO [BfieldcalibrationSchedulerMBean] BfieldcalibrationScheduler has been destroyed
18:32:18,312 WARN [ServiceController] Ignoring request to stop nonexistent service: BfieldServer:service=BfieldCalibrationScheduler

while in 4.0.5 I have

17:59:48,754 INFO [BfieldcalibrationSchedulerMBean] BfieldcalibrationScheduler has been stopped
17:59:48,756 INFO [BfieldcalibrationSchedulerMBean] BfieldcalibrationScheduler has been destroyed
17:59:48,759 WARN [ServiceDelegateWrapper] Stopping failed jboss.j2ee:ear=BfieldServer.ear,jar=BfieldServerBeans.jar,name=BfieldcalibrationSchedulerMBean,service=EJB3
java.lang.RuntimeException: javax.management.InstanceNotFoundException: BfieldServer:service=BfieldCalibrationScheduler is not registered.
 at org.jboss.ejb3.JmxKernelAbstraction.uninstallMBean(JmxKernelAbstraction.java:159)

......etc

The messages are coming when I stop JBoss. The lines printed from my service BfieldcalibrationSchedulerMBean are appearing at the level of the methods stop() and destroy().

The service appear in any case in jmx-console and I can call the exposed methods.

Can you tell me if I'm doing something wrong in 4.0.5 ??

Thanks a lot for any help you can provide

[cinzko]

i have the same problem when i create a jmx-bean with ejb3-annotations when shutting down the server.

did you find a solution yet?
does anyone have the same problem or any suggestions for solving the problem?

[formica]

I did not find a solution, but since it looks harmless, I'm living with this "feature"...nobody else seemed to complain ;-)

May be somebody will reply to you now !

Andrea