Title: Message
Hi Scott,
 
the client-deployer-service.xml uses a an inline model mbean definition. That causes a
 
java.lang.NoSuchMethodException: org.jboss.mx.modelmbean.XMBean.<init>(java.lang.Object, org.w3c.dom.Element, java.lang.String)
        at java.lang.Class.getConstructor0(Class.java:1929)
        at java.lang.Class.getConstructor(Class.java:1019)
        at org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:932)
        at org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:297)
        at org.jboss.mx.server.MBeanServerImpl.createMBean(MBeanServerImpl.java:324)
        at org.jboss.system.ServiceCreator.install(ServiceCreator.java:121)
        at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:151)
        at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:114)
        ... 74 more
 
on statup.
 
    java version "1.4.2_02"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_02-b03)
    Java HotSpot(TM) Client VM (build 1.4.2_02-b03, mixed mode)
 
Hm ..., an XMBean constructor with that signature however exists. Am I looking at a classloading problem?
 
As far as I can see the client-deployer-service.xml it is the only service that does that (inline xmbean) in the 'all' deploy directory. I've taken the liberty to modify the client-deployer-service.xml to use an external mbean definition (that lives in jboss.jar), like this:
 
    <server>
       <mbean code="org.jboss.deployment.ClientDeployer"
          name="jboss.j2ee:service=ClientDeployer"
          xmbean-dd="client-deployer-xmbean.xml">
       </mbean>
    </server>
 
cheers
-thomas
 
PS: If you can't reproduce it, I'm happy look further into it
 
 
 
 

 
 

Reply via email to