Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8231032

ThreadMXBean locking tests fail after JSR 166 refresh

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: P3
    • Resolution: Fixed
    • Affects Version/s: 14
    • Fix Version/s: 14
    • Component/s: core-libs
    • Labels:

      Description

      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

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              martin Martin Buchholz
              Reporter:
              dholmes David Holmes
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: