Bug 534243 (RHQ-1058)

Summary: JON can't get availability/metrics on JVM child services when JBAS uses platform MBean server
Product: [Other] RHQ Project Reporter: Charles Crouch <ccrouch>
Component: DocumentationAssignee: Deon Ballard <dlackey>
Status: CLOSED WONTFIX QA Contact: Mike Foley <mfoley>
Severity: medium Docs Contact:
Priority: low    
Version: 1.1.2CC: asantos, ccrouch, cwelton, dlackey, hbrock, hrupp
Target Milestone: ---Keywords: SubBug
Target Release: ---   
Hardware: All   
OS: All   
URL: http://jira.rhq-project.org/browse/RHQ-1058
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
EAP 4.3.0
Last Closed: 2012-07-18 00:08:06 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 565628    

Description Charles Crouch 2008-11-04 20:57:00 UTC
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


Comment 1 Red Hat Bugzilla 2009-11-10 20:22:59 UTC
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1058


Comment 2 wes hayutin 2010-02-16 16:54:21 UTC
Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs.

keyword:
new = Tracking + FutureFeature + SubBug

Comment 3 wes hayutin 2010-02-16 16:59:48 UTC
making sure we're not missing any bugs in rhq_triage

Comment 4 Greg Hinkle 2010-05-06 16:49:36 UTC
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)

Comment 5 Corey Welton 2010-08-30 17:20:28 UTC
Ian, Deon -- need to find out if this is fixed, and if so, need to doc it.

Comment 6 Deon Ballard 2010-08-30 18:04:22 UTC
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.

Comment 7 Deon Ballard 2012-05-23 22:51:46 UTC
Hey, Charles, is this still something that needs to be documented? Or can it safely be closed?

Comment 8 Deon Ballard 2012-07-18 00:08:06 UTC
Since the underlying JBAS bug is fixed in JBAS 5 and JBAS 4 is deprecated, I'll just close this.