JMX and JBoss

[BP9906]

It appears all the documentation here is related to Tomcat and JMX.
Has anyone had any luck using it with JBoss?

Today I use twiddle.sh to get my information but would be useful to do it using this app.

When I implement it with using port 4447 and dump all in domain "jboss" it comes back with:

processID=0,stanza=jmx://test3,systemErrorMessage="Failed to retrieve RMIServer stub: javax.naming.CommunicationException [Root exception is java.rmi.NoSuchObjectException: no such object in table]"

Any idea what is going on?

[Murali2888]

Did this issue got resolved? I am experiencing the same for jboss 6.3

[Damien_Dallimor]

Do you have the necessary JBoss client jars on the classpath ? (jboss-client.jar)

You can dump a jar file in the "jmx_ta/bin/lib/" directory and it will be automatically loaded.

[BP9906]

Ditto:

07-23-2014 06:57:46.654 -0700 ERROR ExecProcessor - message from "python /opt/splunk/etc/apps/jmx_ta/bin/jmx.py" host=XXXX, jmxServiceURL=service:jmx:remoting-jmx://XXXX:YYYY, jmxport=YYYY, jvmDescription=description, processID=0,stanza=jmx://test1,systemErrorMessage="Unsupported protocol: remoting-jmx"

I copied jmx-client.jar to jmx_ta/bin/lib/ and restarted Splunk and received the above error.

Is the jmx:remoting-jmx service URL supposed to be like this (ie port 1099 and/or different service URI?):
https://community.jboss.org/wiki/JMXRemotingserviceconfiguration

[mschwank]

Hi Damien thanks for the answer, we now get:

07-23-2014 15:54:30.856 +1000 ERROR ExecProcessor - message from "python /app/splunk/etc/apps/jmx_ta/bin/jmx.py" host=10.137.58.xxx, jmxServiceURL=service:jmx:remoting-jmx://hostname:9999, jmxport=9999, jvmDescription=hostname-9999, processID=0,stanza=jmx://hostname,systemErrorMessage="Unsupported protocol: remoting-jmx"

Is there a way to make the remoting-jmx protocol supported in this addon?

Note that I've replaced "hostname" for security reasons

[Damien_Dallimor]

For a custom JMX URL you need to use the jmxServiceURL attribute :

<jmxserver jmxServiceURL="service:jmx:remoting-jmx://hostname:9999" jvmDescription="node2" jmxuser="user" jmxpass="pwd">

...

</jmxserver>

[mschwank]

I've been trying unsuccessfully to get the monitoring of JVMs with JMX to work with Jboss EAP 6.1 with the same error message as BP9906.

It works fine with JConsole, but the Splunk app reports "Failed to retrieve RMIServer stub: javax.naming.CommunicationException [Root exception is java.rmi.NoSuchObjectException: no such object in table]"

Anyone have any clues?

Using service:jmx:remoting-jmx://hostname:9999 in jconsole with a username & pwd, in splunk config.xml

Thanks!

[Damien_Dallimor]

The Monitoring of JVM's with JMX app will work against any JVM with the JMX agent enabled.

I don't know what version of JBoss you are on.

But first , try to connect with JConsole.

This will also allow you to browse which MBeans you are interested in.

Then take the settings you used to connect in JConsole and enter these in your config.xml file for the JMX app to connect to the JBoss JVM's JMX agent.