Please make sure you have done all steps as described above.
JBoss with version 6 is utilizing internally a MBeanServer Factory based on
org.jboss.system.server.jmx.MBeanServerBuilderImpl, however this
one is incompatible
to the default JVM MBeanServerBuilder
Usually this wouldn't be a problem as JBoss when running stand-alone it sets the Platform MBeanService
and all subsequent MBeans will be created from its MBeanServerBuilder.
However when the Wrapper starts, it will register its MBeans and hence the JVM doesn't have a
MBeanServer at this time yet, it will create a MBeanServer using the JVM's default MBeanServer. When
JBoss starts, it tries to register its MBeans to the MBeanServer, however because of the
incompatibility with the default JVM's MBeanServer, JBoss will fail to register any MBean.
In order to use the MBeans of the Wrapper and make it possible for JBoss to register its MBeans,
the JVM needs to get instructed to not use the default Factory but the one used by JBoss, which
is in fact just an extension of the default. In order to do so you need to set the following properties:
Please make sure N is a number, which hasn't been assigned.
In detail the above properties mean, that JBoss should use the platform MBeanServer to register
The JVM should use org.jboss.system.server.jmx.MBeanServerBuilderImpl
as MBeanServer Factory
Hence to that, the Log Manager of the JVM and JBoss have to be redefined. As this Log Manager
is not on the classpath, it also needs to get added there.
After this steps have been done, the Wrapper should be able to run JBoss 6.* without any problems and able to
register it's MBeans side-by-side with JBoss.