Correct GetThreadState return value for Object.wait#21547
Correct GetThreadState return value for Object.wait#21547babsingh merged 1 commit intoeclipse-openj9:masterfrom
Conversation
Signed-off-by: Theresa Mammarella <Theresa.T.Mammarella@ibm.com>
| break; | ||
| case JVMTI_VTHREAD_STATE_PINNED: | ||
| case JVMTI_VTHREAD_STATE_PARKED: | ||
| rc = JVMTI_JAVA_LANG_THREAD_STATE_WAITING | JVMTI_THREAD_STATE_PARKED; |
There was a problem hiding this comment.
JVMTI_JAVA_LANG_THREAD_STATE_WAITING was only introuced in JDK24. Appropriate ifdefs will need to be added. Otherwise, older JDKs will behave incorrectly.
There was a problem hiding this comment.
Are you thinking of JVMTI_VTHREAD_STATE_WAIT? It looks like JVMTI_JAVA_LANG_THREAD_STATE_WAITING has been in the code base for several years.
There was a problem hiding this comment.
You are right. I read too quickly. i will launch the PR builds
|
jenkins test sanity.functional amac jdk24 |
|
jenkins test extended.openjdk amac jdk21,jdk24 |
|
@theresa-m I noticed a new failure that has been documented before. Could you do an initial triage to see if it's related to your changes? If it's not, please create a new issue to track it. Once that's done, I'll go ahead and merge this PR. |
|
It doesn't look related to me, the failing test serviceability/jvmti/ObjectMonitorUsage/ObjectMonitorUsage.java does not call any of the methods that use From the javacore the test looks to be working on Thread.join when the failure occurs: I'll make a new issue for this. |
With this change #21408 passes and #21412 progresses past one failure.