After JDK-8229442 some ThreadMXBean tests fail because they check that the blocker object of a condition wait is a AbstractQueuedSynchronizer$ConditionObject, (not a ConditionNode).
- java/lang/management/ThreadMXBean/SynchronizerLockingThread.java
JavaTest Message: Test threw exception: java.lang.RuntimeException: LockInfo : java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionNode@393b28bb class name not matched. Expected: java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject
- java/lang/management/ThreadMXBean/SynchronizerLockingThread.java
JavaTest Message: Test threw exception: java.lang.RuntimeException: LockInfo : java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionNode@393b28bb class name not matched. Expected: java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject
- relates to
-
JDK-8231036 vmTestbase monitoring tests fail after JSR 166 refresh
-
- Resolved
-
-
JDK-8229442 AQS and lock classes refresh
-
- Resolved
-
1.
|
ProblemList failing ThreadMXBean tests |
|
Resolved | David Holmes |