[jboss-jira] [JBoss JIRA] (WFLY-840) jboss.as MBean subtree missing when profiling agent used

[Brian Stansberry (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry resolved WFLY-840.
-----------------------------------

    Resolution: Done


I'm resolving this as a duplicate of WFLY-895, since per Juliana Loubock's comment, working around the logging issue results in the jboss.as domain mbeans appearing.

> 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-with-jmxetric
> 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 was sent by Atlassian JIRA
(v6.2.6#6264)