JDK-8050115 : [TEST_BUG] javax/management/monitor/GaugeMonitorDeadlockTest.java fails intermittently
  • Type: Bug
  • Component: core-svc
  • Sub-Component: javax.management
  • Affected Version: 7u101,9
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2014-07-12
  • Updated: 2016-01-22
  • Resolved: 2014-09-18
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 7 JDK 8 JDK 9
7u101Fixed 8u40Fixed 9 b32Fixed
Related Reports
Relates :  
JDK-8038322 - CounterMonitorDeadlockTest.java fails intermittently, presumed deadlock
Sub Tasks
JDK-8057937 :  
javax/management/monitor/GaugeMonitorDeadlockTest.java should be quarantined - Resolved
Description
The test
  javax/management/monitor/GaugeMonitorDeadlockTest.java

failed in the 2014-07-11 RT_Baseline nightly with

----------System.err:(14/832)----------
java.lang.Exception: Test failed: presumable deadlock
	at GaugeMonitorDeadlockTest$TestCase.run(GaugeMonitorDeadlockTest.java:110)
	at GaugeMonitorDeadlockTest.main(GaugeMonitorDeadlockTest.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:745)

JavaTest Message: Test threw exception: java.lang.Exception: Test failed: presumable deadlock
JavaTest Message: shutting down test

STATUS:Failed.`main' threw exception: java.lang.Exception: Test failed: presumable deadlock
Comments
Test fix do not need critical request process until GAC build.
22-01-2016
SQE is OK to take it to CPU 16_02.
22-01-2016
This is a test issue - should be integrated in CPU 16_02. No any risks.
22-01-2016
We could not be sure that the test failed of timeout, so we will use test harness timeout to replace the test specified timeout, and add 2 checks in the test. The test verifies deadlock 2 times: 1) during the first verification, for each time (1s * test.timeout.factor) we call threadMXBean.findDeadlockedThreads(), if a deadlock is found, all thread traces will be printed out and the test fails immediately; 2) within the second verification, for each time (1s * test.timeout.factor): 1) all thread traces will be printed out if the tested thread is blocked, but the test will not fail because we are not sure that deadlock happens; 2) otherwise only the trace of the tested thread will be printed out. In case that the test gets interrupted again by the test harness, hope we can have some useful info from these 2 checks.
18-09-2014
ILW=MLH=P4 Creates noise in the test results, happens rarely enough and only on fastdebug builds, no workaround
14-07-2014
The bug with the same manifestation was closed as "Resolved" in 2006: JDK-6424020 The fix was to increase a timeout.
12-07-2014