JDK-8038322 : CounterMonitorDeadlockTest.java fails intermittently, presumed deadlock
  • Type: Bug
  • Component: core-svc
  • Sub-Component: javax.management
  • Affected Version: 7u80,8u20,9
  • Priority: P2
  • Status: Resolved
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 2014-03-25
  • Updated: 2014-09-19
  • Resolved: 2014-09-19
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 9
9Resolved
Related Reports
Duplicate :  
JDK-8031036 - Used for the fix push for JDK-8038322: CounterMonitorDeadlockTest.java fails intermittently, presumed deadlock
Relates :  
JDK-8050115 - [TEST_BUG] javax/management/monitor/GaugeMonitorDeadlockTest.java fails intermittently
Description
The test has failed intermittently on different platforms since 2014-01-14

java.lang.Exception: Test failed: presumable deadlock
	at CounterMonitorDeadlockTest$TestCase.run(CounterMonitorDeadlockTest.java:137)
	at CounterMonitorDeadlockTest.main(CounterMonitorDeadlockTest.java:57)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:484)
	at com.sun.javatest.regtest.MainWrapper$MainThread.run(MainWrapper.java:94)
	at java.lang.Thread.run(Thread.java:744)

RULE javax/management/monitor/CounterMonitorDeadlockTest.java Exception java.lang.Exception: Test failed: presumable deadlock
Comments
The fix was pushed with JDK-8031036
19-09-2014
Similare issue as in JDK-8050115, we could think to use the same solution.
19-09-2014
Possible a timing issue, the test waited about 10*500 ms to check the result. More time may need.
14-04-2014