Intermittent ThreadMXBean/Locks.java test failure

Intermittent failure from my nightly analysis report:

New MM_REGRESSION failures (from 2009.03.06)
    java/lang/management/ThreadMXBean/Locks.java
        This test failed due to "java.lang.RuntimeException: Thread
        WaitingThread is expected to block on java.lang.Object@19968e23
        but got null Thread.State = TIMED_WAITING" on Win-AMD64 Server
        VM -Xcomp (machine vm-v20z-17). This failure mode is described
        by the following bug:

            6736461 4/4 TEST_BUG: ThreadMXBean Locks.java fails intermittently.

        6736461 is in state "fix delivered" for JDK7-B35.

Here is a link to the analysis page:

http://sqeweb.sfbay/nfs/results/vm/gtee/JDK7/NIGHTLY/VM/2009-03-06/RT_Baseline/javase/windows-amd64/server/comp/windows-amd64_server_comp_MM_REGRESSION/analysis.html

Here is a snippet of the .jtr file:

LockBThread about to exit
LockAThread about to exit
WaitingThread about to wait on objC
WaitingThread about to block on ready
----------System.err:(9/657)----------
java version "1.7.0-ea-fastdebug"
Java(TM) SE Runtime Environment (build 1.7.0-ea-fastdebug-b49)
OpenJDK 64-Bit Server VM (build 15.0-b02-2009-03-03-005122.dcubed.fixq-rt-merge-fastdebug, compiled mode)

java.lang.RuntimeException: Thread WaitingThread is expected to block on java.lang.Object@19968e23 but got null Thread.State = TIMED_WAITING
at Locks.checkBlockedObject(Locks.java:64)
at Locks.access$200(Locks.java:37)
at Locks$CheckerThread.run(Locks.java:218)