RHQ 4.7/4.8 JMX plugin viewing application mbeans in JBoss EAP 6.1

[atinject]

Dear All

I am stuck in getting jmx working in RHQ to browse the mbeans that are exposed in our applications running on a jboss eap 6.1 server.

In the image below the jmx item is empty in the left hand side panel? Am I suppose to see the connections through and get the statistics of the mbeans there?

I am aware the jmx connection is done through remoting-connector:

<subsystem xmlns="urn:jboss:domain:jmx:1.2">

        <expose-resolved-model domain-name="XXXX.com"/>

        <expose-expression-model domain-name="XXXX.com"/>

        <remoting-connector use-management-endpoint="false"/>

</subsystem>

In Jconsole (remoting port): service:jmx:remoting-jmx://XXXX.com:4447 connected fine.

Does anyone know why the jmx is not connecting through, I looked at the log it seems to connect using "service:jmx:rmi:///jndi/rmi://localhost:9999/jmxrmi"

Any help would be highly apprecited.

Thanks

Kun

[jayshaughnessy]

RHQ does not have a JConsole-type JMX mbean browser.  The JMX support is used to interact with the mbeans backing metrics or operations defined in RHQ plugins.  For EAP 6.1 there is the AS7 plugin which should discover and report on the appserver.  It provides robust RHQ support for managing EAP6.

[atinject]

Thanks for the reply. I am 100% sure the AS7 plugin doesn't report any mbeans either.

The only to view mbeans is via importing a new JMX Server, the JMX template doesn't reflect to the new jmx remoting protocol since JBoss 7.1+. So I figured out to use JDK5 template and change the connection URL to service:jmx:remoting-jmx://XXXX.com:4447, and it worked out of the box. (only JDK5 template would work in this case.). The JMX plugin code needs to be updated to add template support of the jsr-160 the jmx remoting protocol to talk to JMX servers in a jvm.