[jboss-jira] [JBoss JIRA] Commented: (JGRP-297) Use deadlock detection (JDK 5) to find deadlocks in stress tests or during regular operation

[Bela Ban (JIRA)]

    [ http://jira.jboss.com/jira/browse/JGRP-297?page=comments#action_12342686 ] 
            
Bela Ban commented on JGRP-297:
-------------------------------

Links: 
- java.lang.management package
- Heinz article: http://www.javaspecialists.co.za/archive/newsletter.do?issue=093&locale=en_US and http://www.javaspecialists.co.za/archive/newsletter.do?issue=093&locale=en_US

> Use deadlock detection (JDK 5) to find deadlocks in stress tests or during regular operation
> --------------------------------------------------------------------------------------------
>
>                 Key: JGRP-297
>                 URL: http://jira.jboss.com/jira/browse/JGRP-297
>             Project: JGroups
>          Issue Type: Feature Request
>    Affects Versions: 2.4
>            Reporter: Bela Ban
>         Assigned To: Bela Ban
>             Fix For: 2.5
>
>
> The java.lang.management.ThreadMXBean has a method to check for and (if found) enumerate deadlocked threads (only with simply synchronized locks, jav.util.concurrent locks currently not supported afaik).
> This can be run every N seconds, and is useful in both stress testing and possibly also during operation.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira