I would like to check if JMX can help find hung threads so that I can set up alerts for potential downtime. I'm using a JBoss server.
The java.lang mbean domain has numerous Threading attributes and operations that you can poll into Splunk to perform Thread analysis.
And the JMX App can be setup to access this data in its configuration file (comprehensive examples ship with the install).
It is working now. There was no hung thread in my environment so no data was coming. But I found data is coming when Hung Thread created.
Hi Damien
I have enable operation in configuration file like below:
<operation name="findMonitorDeadlockedThreads" outputname="findMonitorDeadlockedThreads"/>
<operation name="findDeadlockedThreads" outputname="findDeadlockedThreads"/>
But I am not getting any data in Splunk.
Search:
index=* sourcetype="*jmx*" host=xxxxx mbean_domain="java.lang" mbean_property_type=Threading
Result:
host=xx.xx.xx.xx ,jvmDescription="jbossCloudJMX",mbean_domain=java.lang,mbean_property_type=Threading,findDeadlockedThreads=,findMonitorDeadlockedThreads=
Could you please help us if we are doing anything wrong?
What happens if you invoke those operations in JConsole ? Any output ?
Thanks Damien.