Hi,
jboss doesn't use standard jmx protocol but it's own remoting protocol.
I remember working around it by taking jboss-client.jar from jboss and
rebuilding jmxsh.jar. It also required a bit of a code change to get jmxsh
use it. At the end I abandoned the idea of using this approach because the
remoting client seemed to have a memory leak, using up all the heap space -
basically the monitoring was killing jboss apps.
Have a look at Jolokia https://jolokia.org/
It should allow you to query JMX over HTTP.
Regards,
Martin
On 29 March 2017 at 23:14, <user-3444c6d1f06c@xymon.invalid> wrote:
I'm trying to set up jmxstat from xymonton.org to monitor information
about JBoss 7.1 on 64-bit Oracle Linux 6.7 with Java 1.7.0_75. I have
followed the instructions for both the client and server side. The jmxstat
test appears on the Xymon server and is updating every 5 minutes as
expected.
I'm continuously getting the error:
myclient.mydomain.com JMX - connection failed for JVM
I don't know enough about Java or JBoss to know where to start looking.
The instructions for jmxstat say this:
"The JVM will need to be restarted with additional options that enable the
JMX module and define the port & credentials."
What additional options are needed and where are these configured?
The admin port is 9999 and netstat shows that it's listening.
I did use the add-user.sh script to create the username and password in
the mgtm-users.properties file for JBoss.
Any suggestions?
Thanks.