[
https://issues.jboss.org/browse/AS7-6667?page=com.atlassian.jira.plugin.s...
]
dpocock commented on AS7-6667:
------------------------------
David, thanks for the fast response, Jira created the ticket before I had inserted the
description details.
Please see the description, and you will be able to reproduce the problem exactly with the
procedure on my blog.
I've tried it with JDK 1.6.0u38 and 1.7.0u15. I observe the problem with both
7.1.0.Final and 7.1.1.Final
jboss.as MBean subtree missing when profiling agent used
--------------------------------------------------------
Key: AS7-6667
URL:
https://issues.jboss.org/browse/AS7-6667
Project: Application Server 7
Issue Type: Bug
Components: JMX
Affects Versions: 7.1.0.Final
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