Excess threads reporting on deadlock

[Dmytro Sheyko]

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

 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/serviceability-dev/attachments/20121127/35cbdb3a/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: hotspot.diff
Type: application/octet-stream
Size: 3088 bytes
Desc: not available
Url : http://mail.openjdk.java.net/pipermail/serviceability-dev/attachments/20121127/35cbdb3a/hotspot.diff 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: test.diff
Type: application/octet-stream
Size: 7318 bytes
Desc: not available
Url : http://mail.openjdk.java.net/pipermail/serviceability-dev/attachments/20121127/35cbdb3a/test.diff