Ahh, this is a bug I came across about two weeks ago when developing my own
mbean.
It is actually a bug in the MBeanServerImpl when working with mbeans that
use the default domain in the object name (i.e. ":service=Jetty" instead of
"SomeDomain:service=Jetty"). It fails to find the mbean when it tries to
unregister it, even though the call to isRegistered(mbean) returns true.
Put a domain name in your object name the problem goes away.
David.
> -----Original Message-----
> From: Julian Gosnell [mailto:[EMAIL PROTECTED]]
> Sent: Monday, September 17, 2001 12:09 PM
> To: [EMAIL PROTECTED]
> Subject: [JBoss-dev] JSR/SAR (Jetty) Undeployment...
>
>
>
> Hot-deploying the Jetty service works fine.
>
> Hot-undeploying generates the following exception :
>
>
> [AutoDeployer] Auto undeploy of
> file:/mnt/megalodon/home/jules/cvs/JBoss/3.0/build/output/jbos
> s-3.0.0alpha/deploy/jetty-service.xml
>
> [JettyService] Stopping
> [Jetty] Stopped SocketListener on 0.0.0.0:8080
> [JettyService] Stopped
> [JettyService] Destroying
> [Jetty] Destroy SocketListener on 0.0.0.0:8080
> [Jetty] Deregister Jetty:Jetty=0,SocketListener=0
> [JettyService] Destroyed
> [ServiceDeployer] Mbean exception while executing undeploy on
> [Ljava.lang.Object;@333a0e
> javax.management.InstanceNotFoundException: :service=Jetty
> at
> com.sun.management.jmx.MBeanServerImpl.unregisterMBean(MBeanSe
> rverImpl.java:945)
>
> at
> org.jboss.system.ServiceController.undeploy(ServiceController.
> java:248)
> at java.lang.reflect.Method.invoke(Native Method)
> at
> com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.
> java:1628)
>
> at
> com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.
> java:1523)
>
> at
> org.jboss.deployment.ServiceDeployer.invoke(ServiceDeployer.java:949)
> at
> org.jboss.deployment.ServiceDeployer.undeploy(ServiceDeployer.
> java:681)
> at java.lang.reflect.Method.invoke(Native Method)
> at
> com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.
> java:1628)
>
> at
> com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.
> java:1523)
>
> at org.jboss.deployment.AutoDeployer.undeploy(AutoDeployer.java:664)
> at org.jboss.deployment.AutoDeployer.run(AutoDeployer.java:270)
> at java.lang.Thread.run(Thread.java:484)
>
> It looks like the service was located and successfully shut down and
> destroyed. Then something went wrong.
>
> Is this a known problem in undeployment, or something peculiar to the
> Jetty service.
>
> Perhaps Jetty's own MBeans are confusing the issue - I'll run some
> tests...
>
>
> I would like to get it fixed, as it will speed my development cycle
> substantially if I can bounce just the Jetty service, and not
> the whole
> server, each time I recompile my stuff.
>
>
> Thanks, Guys,
>
>
>
> Jules
>
>
>
>
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
