[
https://issues.jboss.org/browse/WFLY-840?page=com.atlassian.jira.plugin.s...
]
Juliana Louback commented on WFLY-840:
--------------------------------------
To fix the JBoss crash issue (JBoss crashes when run with AspectJ java agent -
https://issues.jboss.org/browse/WFLY-895) I commented out the logging in jmxetric. After
this, JBoss ran with the jmxetric without a problem. But in addition to this, after
removing the logging all the subtrees were visible when connecting with jconsole - or at
least, the jboss.as MBean subtree was present as were all the other trees listed
(jboss.modules, jboss.ws, jboss.msc, jboss.jta).
My github account has a jmxetric branch that removes the logging (as well as other
modifications):
https://github.com/JLouback/jmxetric/tree/logbranch
jboss.as MBean subtree missing when profiling agent used
--------------------------------------------------------
Key: WFLY-840
URL:
https://issues.jboss.org/browse/WFLY-840
Project: WildFly
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMX
Reporter: dpocock
Labels: jconsole
I've set up JBoss 7.1.0.Final as a fresh installation and started standalone
I can successfully connect with regular jconsole or $JBOSS_HOME/bin/jconsole. In the
MBeans tab, I can see various subtrees, including jboss.as
Then I stop JBoss and add the jmxetric monitoring agent, as described here:
http://danielpocock.com/monitoring-jboss-tomcat-and-application-servers-w...
Now, with JBoss running with jmxetric, I connect to it with jconsole (either regular
jconsole or $JBOSS_HOME/bin/jconsole) and I can see all the same subtrees, except one,
jboss.as is missing. I can see jboss.modules, jboss.ws, jboss.msc, jboss.jta and core JVM
subtrees
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira