I think this is probably just something which needs to be documented, since it appears to fundamentally be a JBAS issue (https://jira.jboss.org/jira/browse/JBAS-5220) Basically in my testing of accessing JBAS's JVM mbean server through a remote interface if the following are set JAVA_OPTS="$JAVA_OPTS -Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl" JAVA_OPTS="$JAVA_OPTS -Djboss.platform.mbeanserver" then all of the JVM's child services, e.g. Class Loading, show red and collect no metrics. If you leave out JAVA_OPTS="$JAVA_OPTS -Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl" then the EAP4.3 instance I was testing wouldn't even start: Failed to boot JBoss: javax.management.InstanceNotFoundException: JMImplementation:service=LoaderRepository,name=Default The workaround would seem, according to https://jira.jboss.org/jira/browse/JBPAPP-658, to be use EAP4.3 CP01
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1058
Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs. keyword: new = Tracking + FutureFeature + SubBug
making sure we're not missing any bugs in rhq_triage
This effectively was fixed by detecting that the jvm is using jmx-remoting and attempting to make a separate jmx-remoting connection for the jvm resources. There appears to be an issue with reconnecting this when the jvm is rebooted though. (See EmbeddedJMXServerDiscoveryComponent for details)
Ian, Deon -- need to find out if this is fixed, and if so, need to doc it.
This is not doc'ed yet, I know that. If it is not fixed or won't be fixed, I'll add it to the 2.4 docs.
Hey, Charles, is this still something that needs to be documented? Or can it safely be closed?
Since the underlying JBAS bug is fixed in JBAS 5 and JBAS 4 is deprecated, I'll just close this.