Monitoring JBOSS (JMX)

Hi,

Currently, we try to monitor JBOSS with Solarwinds.

As far as we know, we have to configure the JVM for JMX and add some Java arguments at the startup file /run.sh.

We also follow this article below :

After we add the Java arguments, we restart the service in order to make it works.

The problem is, the application can not start anymore and we can't even try to monitor this JBoss.

My question is, is the configurastion from the article can be used for any version of JBoss ? (We used JBoss Version 6.2).

Are there any prerequisites before we do this configuration ?

Find more posts tagged with

This has been tested on a few different versions. Have you opened a support case to troubleshoot further?

Hi Rio,

it seems that for JBoss 7.2+ (aka EAP 6.1+) is possible configure JMX remoting without touching the JVM startup parameters.

For me was working on the standalone configuration such steps:

call .\bin\add-user.bat to add a user for monitoring (select Management User, About to add user '...' for realm 'ManagementRealm' Is this correct yes/no? YES)
modify configuration .\standalone\configuration\standalone.xml - to listen on IP address - screenshot shows how to configure for any address.
You will probably use more strict settings to allow access just from Orion server.

Alternative for this step is to use parameter -Djboss.bind.address.management 2015-02-13 16_06_32-10.199.7.16 - Jboss config.png

start it using .\bin\standalone.bat
check from command-line, that machine listen on port 9990 or 9999 netstat -ano
an additional check can be done using JConsole from Orion server - to be sure that JMX remoting is working outside Solarwinds Orion environment as well
In SAM template/application change mBeans "Custom URL Format:" - JMX templates require configuration changes for SAM 6.3 - SolarWinds Worldwide, LLC. Help and Support
1. for JBoss 7.x : service:jmx:remoting-jmx://${IP}:9999
2. for WildFly 8.2: service:jmx:http-remoting-jmx://${IP}:9990
modify Solarwinds JMX bridge configuration to use newer JBoss libraries, as described in https://thwack.solarwinds.com/ideas/4434#comment-230598