Bug ID: JDK-4980307 JVMTI Spec: thread state query should allow for future expansion

Type: Enhancement
Component: hotspot
Sub-Component: jvmti
Affected Version: 5.0

Priority: P2
Status: Resolved
Resolution: Fixed
OS: generic
CPU: generic

Submitted: 2004-01-20
Updated: 2017-05-16
Resolved: 2004-02-12

Versions (Unresolved/Resolved/Fixed)

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.

Other
5.0 b38Fixed

The current GetThreadStatus returns an ordinal indicating the thread status.
What we have learned from this (and similar functionality) is that an ordinal
return values break everytime a new state is added or more detail is provided.
There is also no allowance for partial information -- for example, a VM may
know it is waiting but not know further details.

CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: tiger-beta2 FIXED IN: tiger-beta2 INTEGRATED IN: tiger-b38

14-06-2004

SUGGESTED FIX The proposed solution is to provide a hierarchical thread state that solves both problems. This state is represented as a bit vector. To allow for a smooth transition the existing GetThreadStatus will be deprecated then removed before release. A new GetThreadState will be added to replace it. ###@###.### 2004-01-19

19-01-2004

EVALUATION See Description and Suggested Fix ###@###.### 2004-01-19

19-01-2004

Duplicate :	JDK-4939080 - JVMTI spec: jvmtiThreadStatus should match java.lang.management.ThreadState
Relates :	JDK-5028424 - JVMTI Spec: Align GetThreadState bits with java.lang.Thread.State
Relates :	JDK-4998297 - JVMTI Spec: Remove GetThreadStatus which was deprecated in 4980307