#6 Updated to wildfly-8.1.0: - MBean jboss.system:type=ServerInfo could not be found

[xxjobexx]

Hi,
recently we updated our environment from Jboss-4.2.3 to wildfly-8.1.0, so I installed the latest version of your plugin: deployment completes normally, but nagios check now returns:

UNKNOWN ACTIVETHREADCOUNT UNKNOWN - MBean jboss.system:type=ServerInfo could not be found

Nagios check runs with these parameters: check_mbean_collector -H server_name -p 5566 -m java.lang:type=Memory -a ActiveThreadCount -w 200 -c 400

Do you know what is the new name of the mbean for wildfly 8.1.0?

[xxjobexx]

Sorry, wrong copy-paste in the previous post... the correct nagios check is:

check_mbean_collector -H server_name -p 5566 -m jboss.system:type=ServerInfo -a ActiveThreadCount -w 200 -c 400

[Tobias Frech]

Since WildFly does no longer provide these MBeans but instead uses the default JVM MBean server you might want try this (hadn't time to test so far):

MBean: java.lang:type=Threading
Attribute: ThreadCount

check_mbean_collector -H server_name -p 5566 -m java.lang:type=Threading -a ThreadCount -w 200 -c 400

If you start the jconsole.sh commmand from the WildFly bin directory and select a running WilfFly-process you can see a lot of MBeans on the MBeans tab. The MBean-name in complete is given as the "ObjectName". The attributes are listed when selecting "Attributes" below a MBean.

[xxjobexx]

It worked! The command you provided checks for thread number correctly.
Thanks!