JDK-6272462 : SA: Print java.util.concurrent locks for jstack -l on core file or hung processes
  • Type: Enhancement
  • Component: core-svc
  • Sub-Component: tools
  • Affected Version: 5.0
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2005-05-18
  • Updated: 2010-08-24
  • Resolved: 2005-08-26
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6
6 b49Fixed
Related Reports
Relates :  
Relates :  
Description
Control-break/SIGQUIT thread dump now is printing java.util.concurrent locks information.  In addition, it will detect deadlocks involved in object monitors as well as java.util.concurrent locks. See 5086430.

jstack now has a new -l option to print additional information about j.u.c. locks.  6266583 adds the support in the VM_ThreadDump for jstack -l <pid>.  The last piece is to port this j.u.c locks support to SA.
###@###.### 2005-05-18 16:45:20 GMT

Comments
EVALUATION Please refer to "Suggested Fix" for changes for this bug.
17-08-2005

SUGGESTED FIX Webrev: http://bongo.india/debugging/sa/6232129-and-6272462/1.6.0/webrev/ Also, referred to attachment "webrev.tar". This webrev includes fix for another (unrelated) SA RFE 6232129 and Linux pathmap feature. *** (#1 of 1): [ UNSAVED ] ###@###.###
17-08-2005

EVALUATION This is more or less porting of deadlock, lock listing code in threadService.cpp file in hotspot code.
12-08-2005