-
Enhancement
-
Resolution: Duplicate
-
P3
-
None
-
5.0
-
generic
-
generic
1) Names should match (ThreadState has better names, so JVMTI should change):
JVMTI_THREAD_STATUS_ZOMBIE ==> JVMTI_THREAD_STATUS_TERMINATED
JVMTI_THREAD_STATUS_MONITOR ==> JVMTI_THREAD_STATUS_BLOCKED
Old names should remain additionally to allow a smooth transition but
must be removed before release.
2) Not all platforms can provide JVMTI_THREAD_STATUS_IO_WAIT, so it should
be conditional on a capability: can_get_io_wait_status
3) The constants should be renumbered so as to be in a reasonable order,
to be non-negative, to allow for the above, and to be unique.
JVMTI_THREAD_STATUS_ZOMBIE ==> JVMTI_THREAD_STATUS_TERMINATED
JVMTI_THREAD_STATUS_MONITOR ==> JVMTI_THREAD_STATUS_BLOCKED
Old names should remain additionally to allow a smooth transition but
must be removed before release.
2) Not all platforms can provide JVMTI_THREAD_STATUS_IO_WAIT, so it should
be conditional on a capability: can_get_io_wait_status
3) The constants should be renumbered so as to be in a reasonable order,
to be non-negative, to allow for the above, and to be unique.
- duplicates
-
JDK-4950589 JVMTI spec: thread status constants - normalize names, renumber, add park
-
- Closed
-
-
JDK-4980307 JVMTI Spec: thread state query should allow for future expansion
-
- Resolved
-
- relates to
-
JDK-4639363 Java Platform Profiling Architecture (JSR-163)
-
- Resolved
-
-
JDK-4937022 JVMTI spec: need JVMTI_THREAD_STATUS_IO_WAIT
-
- Closed
-