-
Enhancement
-
Resolution: Fixed
-
P3
-
None
-
b26
1. The implementation is changed to use a thread handshake to get a consistent snapshot of each thread.
2. The updated thread dump includes the thread state, the object if a thread is blocked on monitor enter, the parkParker if the thread is parked, the owner when the parkParker is an ownable synchronizer, and the frames where object monitors have been entered.
3. If HotSpotDiagnosticMXBean.dumpThreads throws IOException but not when writing to the file system fails. This should be fixed.
4. HotSpotDiagnosticMXBean.dumpThreads links to a JSON schema that describes the JSON format.
- csr for
-
JDK-8356872 HotSpotDiagnosticMXBean.dumpThreads and jcmd Thread.dump_to_file updates
-
- Closed
-
- duplicates
-
JDK-8302184 full lock information for virtual threads in thread dumps
-
- Closed
-
-
JDK-8287080 Document format of thread dump in JSON format
-
- Closed
-
- relates to
-
JDK-8360554 Use the title from the JSON RFC for the @spec tag
-
- Resolved
-
-
JDK-8360599 Test DumpThreadsWithEliminatedLock.java fails on ppc64(le) platforms
-
- New
-
-
JDK-8284296 Thread dump issues
-
- Open
-
- links to
-
Commit(master) openjdk/jdk/f17b2bc0
-
Review(master) openjdk/jdk/25429