-
Bug
-
Resolution: Fixed
-
P2
-
9
-
b75
-
generic
-
generic
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8135618 | emb-9 | Daniel Daugherty | P2 | Resolved | Fixed | team |
In the 2015-07-14 RT_Baseline nightly, the following tmtools tests are
failing in most configurations:
tmtools/jstack/locks/wait_interrupt
tmtools/jstack/locks/wait_notify
In the wait_interrupt server.log file:
[2015-07-15T03:30:42.27] Test tesults:
[2015-07-15T03:30:42.27] FAILED: wait_interrupt. The reason: Analysers fail:
[2015-07-15T03:30:42.27] nsk.share.Failure: Analysers fail:
[2015-07-15T03:30:42.27] tmtools.jstack.share.debuggee.WaitInterruptDebuggee.run method has to contain only one lock record
[2015-07-15T03:30:42.27]
[2015-07-15T03:30:42.27] at tmtools.share.Test.doTest(Test.java:246)
[2015-07-15T03:30:42.27] at tmtools.share.TestSuite.execute(TestSuite.java:172)
[2015-07-15T03:30:42.27] at tmtools.share.TestSuite.main(TestSuite.java:206)
[2015-07-15T03:30:42.27] tmtools.jstack.share.debuggee.WaitInterruptDebuggee.run method has to contain only one lock record
[2015-07-15T03:30:42.27]
In the wait_notify server.log file:
[2015-07-15T03:30:33.43] Test tesults:
[2015-07-15T03:30:33.43] FAILED: wait_notify. The reason: Analysers fail:
[2015-07-15T03:30:33.43] nsk.share.Failure: Analysers fail:
[2015-07-15T03:30:33.43] tmtools.jstack.share.debuggee.WaitNotifyDebuggee$WaitThread.run method has to contain only one lock record
[2015-07-15T03:30:33.43]
[2015-07-15T03:30:33.43] at tmtools.share.Test.doTest(Test.java:246)
[2015-07-15T03:30:33.43] at tmtools.share.TestSuite.execute(TestSuite.java:172)
[2015-07-15T03:30:33.43] at tmtools.share.TestSuite.main(TestSuite.java:206)
[2015-07-15T03:30:33.43] tmtools.jstack.share.debuggee.WaitNotifyDebuggee$WaitThread.run method has to contain only one lock record
failing in most configurations:
tmtools/jstack/locks/wait_interrupt
tmtools/jstack/locks/wait_notify
In the wait_interrupt server.log file:
[2015-07-15T03:30:42.27] Test tesults:
[2015-07-15T03:30:42.27] FAILED: wait_interrupt. The reason: Analysers fail:
[2015-07-15T03:30:42.27] nsk.share.Failure: Analysers fail:
[2015-07-15T03:30:42.27] tmtools.jstack.share.debuggee.WaitInterruptDebuggee.run method has to contain only one lock record
[2015-07-15T03:30:42.27]
[2015-07-15T03:30:42.27] at tmtools.share.Test.doTest(Test.java:246)
[2015-07-15T03:30:42.27] at tmtools.share.TestSuite.execute(TestSuite.java:172)
[2015-07-15T03:30:42.27] at tmtools.share.TestSuite.main(TestSuite.java:206)
[2015-07-15T03:30:42.27] tmtools.jstack.share.debuggee.WaitInterruptDebuggee.run method has to contain only one lock record
[2015-07-15T03:30:42.27]
In the wait_notify server.log file:
[2015-07-15T03:30:33.43] Test tesults:
[2015-07-15T03:30:33.43] FAILED: wait_notify. The reason: Analysers fail:
[2015-07-15T03:30:33.43] nsk.share.Failure: Analysers fail:
[2015-07-15T03:30:33.43] tmtools.jstack.share.debuggee.WaitNotifyDebuggee$WaitThread.run method has to contain only one lock record
[2015-07-15T03:30:33.43]
[2015-07-15T03:30:33.43] at tmtools.share.Test.doTest(Test.java:246)
[2015-07-15T03:30:33.43] at tmtools.share.TestSuite.execute(TestSuite.java:172)
[2015-07-15T03:30:33.43] at tmtools.share.TestSuite.main(TestSuite.java:206)
[2015-07-15T03:30:33.43] tmtools.jstack.share.debuggee.WaitNotifyDebuggee$WaitThread.run method has to contain only one lock record
- backported by
-
JDK-8135618 tmtools/jstack/locks/wait_interrupt and wait_notify fail due to wrong number of lock records
-
- Resolved
-
- relates to
-
JDK-8130448 thread dump improvements, comment additions, new diagnostics inspired by 8077392
-
- Resolved
-
-
JDK-8131694 backout the fix for JDK-8131331 when JDK-8131693 is fixed
-
- Resolved
-