Hi,

I would like to propose a patch regarding deadlock detection.
Excess threads reporting on deadlock
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6850341
https://bugs.openjdk.java.net/show_bug.cgi?id=100065

Deadlock detection mechanism (ThreadMXBean.findMonitorDeadlockedThreads() and 
ThreadMXBean.findDeadlockedThreads()) reports not only threads that are 
involved in deadlock directly, but also some threads that are blocked but out 
of any deadlock cycle.

The idea is to remember the first thread that starts cycle. And start iteration 
from that leader in places where DeadlockCycle is used to iterate deadlocked 
threads.

Regards,
Dmytro

                                          

Attachment: hotspot.diff
Description: Binary data

Attachment: test.diff
Description: Binary data

Reply via email to