http://jira.hyperic.com/browse/HHQ-1961
After running the server under heavy load for a day I am seeing following java level deadlock in HQ's thread dump.
The server configuration has ~50K classic value change alerts. All of them are disabled and inactive.
Full thread dump is attached. I see another issue in there and will open another bug for it.
Found one Java-level deadlock:
=============================
"Thread-19":
waiting to lock monitor 0x0000000049d2f718 (object 0x00002aab0df1b4a8, a java.lang.Object),
which is held by "ZeventProcessor"
"ZeventProcessor":
waiting to lock monitor 0x0000000049d2fda8 (object 0x00002aab0df1b418, a java.lang.Object),
which is held by "Thread-19"
Java stack information for the threads listed above:
===================================================
"Thread-19":
at org.hyperic.hq.zevents.ZeventManager.getDiagnostics(ZeventManager.java:575)
- waiting to lock <0x00002aab0df1b4a8> (a java.lang.Object)
- locked <0x00002aab0df1b418> (a java.lang.Object)
at org.hyperic.hq.zevents.ZeventManager.access$000(ZeventManager.java:65)
at org.hyperic.hq.zevents.ZeventManager$1.getStatus(ZeventManager.java:168)
at org.hyperic.hq.common.DiagnosticThread.run(DiagnosticThread.java:115)
- locked <0x00002aab0a24f9c0> (a java.util.ArrayList)
at java.lang.Thread.run(Unknown Source)
"ZeventProcessor":
at org.hyperic.hq.zevents.ZeventManager.getListenerTimeout(ZeventManager.java:219)
- waiting to lock <0x00002aab0df1b418> (a java.lang.Object)
at org.hyperic.hq.zevents.ZeventManager.dispatchEvents(ZeventManager.java:546)
- locked <0x00002aab0df1b4a8> (a java.lang.Object)
at org.hyperic.hq.zevents.QueueProcessor.processBatch(QueueProcessor.java:79)
at org.hyperic.hq.zevents.QueueProcessor.run(QueueProcessor.java:61)
at java.lang.Thread.run(Unknown Source)
Found 1 deadlock.
Anonymous