Red Hat Bugzilla – Bug 534499
JBAS JVM's discovered as sibling servers (not children) when jmx remoting is enabled
Last modified: 2015-02-01 18:24:51 EST
Typically when you discover a JBAS instance (if you have the platform mbeanserver option enabled) you get the JVM resource brought in as well as a child server of the JBAS server. However if you start JBAS with jmx remoting enabled, the JVM will be discovered as a sibling server to JBAS.
This is unintuitive since just because the JVM is accessible remotely, doesn't change the fact its used to run JBAS.
jay, can you think about this and figure out how you propose this work for your work with the tomcat plugin. ping me if you need additional details.
I think this is the same problem we had with the Tomcat Server being discoverd both as a Tomcat Server and as a JMX Server. This is because the JMX plugin picks up every process with "com.sun.management.jmxremote.port" in the command line. I already added a simple filter mechanism to ignore Tomcat servers, perhaps I can just add another filter for this.
pushing to future as the workaround is acceptable for now.
What was the workaround?
I found it - IMO, that needs to be taken out. We should not code in specific things into an RHQ plugin to handle Jopr plugins.
What if someone doesn't have a Jopr plugin and wants to monitor Tomcat VM?
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1290
Moving this old bug to ON_QA to see if it still exists. Close if no longer an issue, reopen if issue still exists.
If this bug is lacking repro steps, please contact joseph.
Tested on jon-2.4GA
Started EAP5.1 with jmx remoting enabled by inserting below lines in run.conf
JAVA_OPTS="$JAVA_OPTS -Xms512m -Xmx512m"
JAVA_OPTS="$JAVA_OPTS -XX:PermSize=192m -XX:MaxPermSize=192m"
JAVA_OPTS="$JAVA_OPTS -XX:NewSize=128m -XX:MaxNewSize=128m"
The JVM resource is discovered as a child server.
Please refer the attached screenshot.
Created attachment 437834 [details]
Mass-closure of verified bugs against JON.