| US 7,502,968 B2 | ||
| Automated hang detection in java thread dumps | ||
| Michel Betancourt, Morrisville, N.C. (US); Dipak M. Patel, Morrisville, N.C. (US); and Chintamani Sahoo, Cary, N.C. (US) | ||
| Assigned to International Business Machines Corporation, Armonk, N.Y. (US) | ||
| Filed on Jul. 26, 2007, as Appl. No. 11/828,916. | ||
| Application 11/828916 is a continuation of application No. 10/632062, filed on Jul. 31, 2003, granted, now 7,278,057. | ||
| Prior Publication US 2008/0046782 A1, Feb. 21, 2008 | ||
| This patent is subject to a terminal disclaimer. | ||
| Int. Cl. G06F 11/00 (2006.01) | ||
| U.S. Cl. 714—38 [717/131; 718/100; 718/104; 707/8; 711/150] | 5 Claims |
| 1. A method of analyzing thread deadlocks in a Java virtual machine (JVM), comprising the steps of:
obtaining a thread dump file;
identifying a locked object in the thread dump file, wherein the locked object is indicated as being in use by an active thread;
identifying any waiting threads that are associated with the locked object, wherein the waiting threads are threads that are
waiting on the locked object;
identifying any locking threads that are associated with the locked object, wherein the locking threads are threads that own
a resource and are currently attempting to lock the locked object; and
comparing the waiting threads and the locking threads to identify any self threads in a self wait condition, wherein a self
thread in a self wait condition is the active thread that currently owns the locked object and is also one of the waiting
threads that is waiting on the locked object and matches one of the locking threads, wherein a user interface allows a user
to choose rules, and wherein the rules are used to exclude threads that are identified as being in a self wait condition from
being identified as in a deadlock condition.
|