You might check that the plugin and the MBean is working properly by doing a test run on the Nagios server:
./check_mbean_collector -H jbossserver -p 5566 -m jboss.system:type=ServerInfo -a ActiveThreadCount -w 200 -c 400
Please note that you need the nagios-plugins package installed and of course replace "jbossserver" above with you server name.
Retrieve some MBean attribute value from a JBoss server through the collector MBean:
check_mbean_collector -H host -p port -m mbean_name -a attribute_name -w warning_level -c critical_level
Usage:
check_mbean_collector -H host[,host,..] -p port -m mbean-name -a attribute-name -w warning-level -c critical-level
check_mbean_collector [-h | --help]
check_mbean_collector [-V | --version]
<host> The server running JBoss.
Giving a comma separated list of hosts switches to a check for a singleton in a cluster.
<port> The port the deployed collector MBean is listening to
<mbean_name> The JMX name of the MBean that includes the attribute, e.g. jboss.system:type=ServerInfo
Use the ${some.env} notation to refer to a JVM environment variable on the server.
In Nagios config files this must be escaped like this: $$\\{some.env}
<attribute_name> The name of the MBean attribute to retrieve, e.g. ActiveThreadCount
Prefix with * to get the difference between two calls (delta). ${...} can be used.
<warning_level> The level as a number from which on the WARNING status should be set
<critical_level> The level as a number from which on the CRITICAL status should be set