Bug 30963 - JBoss 4.0.5 fails to start with MBeanServer exception
Summary: JBoss 4.0.5 fails to start with MBeanServer exception
Status: RESOLVED FIXED
Alias: None
Product: classpath
Classification: Unclassified
Component: classpath (show other bugs)
Version: unspecified
: P3 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-02-25 20:01 UTC by Paul Jenner
Modified: 2007-04-08 19:44 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:
Known to work:
Known to fail:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Jenner 2007-02-25 20:01:05 UTC 
JBoss 4.0.5 fails to start on Classpath HEAD with error:

19:52:17,557 WARN  [ServiceController] Problem creating service jboss.system:service=MainDeployer
java.lang.IllegalStateException: No 'jboss' MBeanServer found!
   at org.jboss.mx.util.MBeanServerLocator.locateJBoss(MBeanServerLocator.java:122)
   at org.jboss.mx.util.MBeanProxyExt.create(MBeanProxyExt.java:335)
   at org.jboss.system.server.ServerConfigLocator.locate(ServerConfigLocator.java:42)
   at org.jboss.deployment.MainDeployer.createService(MainDeployer.java:471)
   at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)
   at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243)
   at java.lang.reflect.Method.invokeNative(Native Method)
   at java.lang.reflect.Method.invoke(Method.java:355)
   at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
   at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
   at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
   at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
   at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
   at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
   at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
   at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
   at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
   at $Proxy0.create(Unknown Source)
   at org.jboss.system.ServiceController.create(ServiceController.java:330)
   at org.jboss.system.ServiceController.create(ServiceController.java:273)
   at java.lang.reflect.Method.invokeNative(Native Method)
   at java.lang.reflect.Method.invoke(Method.java:355)
   at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
   at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
   at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
   at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
   at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
   at org.jboss.system.server.ServerImpl.startBootService(ServerImpl.java:564)
   at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:446)
   at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
   at org.jboss.Main.boot(Main.java:200)
   at org.jboss.Main$1.run(Main.java:490)
   at java.lang.Thread.run(Thread.java:743)
   at java.lang.VMThread.run(VMThread.java:120)

A similar problem is logged trying to create the other initial deployer services.
Comment 1 Andrew John Hughes 2007-02-28 15:57:38 UTC 
This is a strange stack trace; I can't see any of our code in it.
Comment 2 Paul Jenner 2007-02-28 19:08:13 UTC 
Apologies - this was the stacktrace logged in JBoss. I didn't go through it - just wanted to get something logged. I'll try to get better detail.

I can confirm this works fine with Classpath 0.92 but fails with Classpath CVS however.
Comment 3 Andrew John Hughes 2007-03-07 22:47:39 UTC 
Thanks; I didn't mean to criticise, but clearly it's pretty difficult to do anything with the current trace.  It wouldn't surprise me if behaviour has changed between 0.92 and CVS, as Classpath now has a partial management implementation which (IIRC) wasn't present in 0.92.
Comment 4 Paul Jenner 2007-03-31 14:36:15 UTC 
Fixed for me by this patch by Andrew Haley:

http://developer.classpath.org/pipermail/classpath-patches/2007-March/005202.html

Awaits committing.
Comment 5 Paul Jenner 2007-04-08 19:44:50 UTC 
Fixed by this commit:

2007-04-02  Andrew Haley  <address@hidden>

        * javax/management/ObjectName.java: Handle 0-length names.
        * javax/management/MBeanServerFactory.java: Use the domain that
        we've been passed, not the fixed string "DefaultDomain".