Upon furthur investigation it seems that this is not a problem unique to my 
test code. The mdb-standalone example in the emdedded-tutorials also fails to 
shutdown properly throwing the warning


  |  [java] WARN  06-07 08:09:59,992 (ServiceMBeanSupport.java:stop:210)  
-Error in stop jboss.mq:service=StateManager
  |      [java] javax.management.InstanceNotFoundException: 
jboss.system:service=ServiceController
  |      [java]     at 
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1010)
  |      [java]     at 
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:804)
  |      [java]     at 
com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
  |      [java]     at 
org.jboss.system.ServiceMBeanSupport.stop(ServiceMBeanSupport.java:204)
  |      [java]     at 
jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown
 Source)
  |      [java]     at 
java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;J)Ljava.lang.Object;(Unknown
 Source)
  |      [java]     at 
org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:55)
  |      [java]     at 
org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:107)
  |      [java]     at 
org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66)
  |      [java]     at 
org.jboss.kernel.plugins.dependency.KernelControllerContextActions.dispatchJoinPoint(KernelControllerContextActions.java:100)
  |      [java]     at 
org.jboss.kernel.plugins.dependency.KernelControllerContextActions$LifecycleAction.uninstallAction(KernelControllerContextActions.java:604)
  |      [java]     at 
org.jboss.kernel.plugins.dependency.KernelControllerContextActions$KernelControllerContextAction.uninstall(KernelControllerContextActions.java:219)
  |      [java]     at 
org.jboss.dependency.plugins.AbstractControllerContextActions.uninstall(AbstractControllerContextActions.java:58)
  |      [java]     at 
org.jboss.dependency.plugins.AbstractControllerContext.uninstall(AbstractControllerContext.java:236)
  |      [java]     at 
org.jboss.dependency.plugins.AbstractController.uninstall(AbstractController.java:605)
  |      [java]     at 
org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:575)
  |      [java]     at 
org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:510)
  |      [java]     at 
org.jboss.dependency.plugins.AbstractController.uninstall(AbstractController.java:194)
  |      [java]     at 
org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.undeployBean(AbstractKernelDeployer.java:367)
  |      [java]     at 
org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.undeployBeans(AbstractKernelDeployer.java:346)
  |      [java]     at 
org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.undeploy(AbstractKernelDeployer.java:149)
  |      [java]     at 
org.jboss.ejb3.embedded.EJB3StandaloneBootstrap.shutdown(EJB3StandaloneBootstrap.java:332)
  |      [java]     at org.jboss.tutorial.mdbstandalone.Main.main(Main.java:60)
  | 

The problem only seems to occur when trying to use jms with the embedded 
server. I don't see any mention of this problem on Jira. Is this a known bug?

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3955822#3955822

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3955822

Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to