|
Quick Lists
|
|
Bug ID:
|
6732441
|
|
Votes
|
0
|
|
Synopsis
|
TEST_BUG: ThreadMXBeanProxy test fails intermittently
|
|
Category
|
java:classes_management
|
|
Reported Against
|
|
|
Release Fixed
|
7(b34)
|
|
State
|
10-Fix Delivered,
bug
|
|
Priority:
|
4-Low
|
|
Related Bugs
|
|
|
Submit Date
|
31-JUL-2008
|
|
Description
|
Following test fails intermittently.
java/lang/management/ManagementFactory/ThreadMXBeanProxy.java
This test failed due to "RuntimeException: Number of locked
syncs = 0 not matched. Expected: 1" on Solaris X86 Server VM
(machine vm-amd64- customer ).
Failure log:
http://sqeweb.sfbay.sun.com/nfs/results/vm/gtee/JDK7/NIGHTLY/VM/2008-07-17/Serv_Baseline/javase/solaris-i586/server/mixed/javase-solaris-i586_server_mixed_MM_REGRESSION2008-07-17-19-43-00/workDir/java/lang/management/ManagementFactory/ThreadMXBeanProxy.jtr
java.lang.RuntimeException: Number of locked syncs = 0 not matched. Expected: 1
at ThreadMXBeanProxy$MyThread.checkThreadInfo(ThreadMXBeanProxy.java:162)
at ThreadMXBeanProxy.main(ThreadMXBeanProxy.java:80)
Posted Date : 2008-07-31 23:29:10.0
|
|
Work Around
|
N/A
|
|
Evaluation
|
This is due to bug in the test case. Problem is main thread calls checkThreadInfo() before the MyThread mutex.lock() sets the owner thread. Solution is to add Thread.sleep() in main thread
to give a chance to MyThread to set the exclusive owner of lock in the test case.
Posted Date : 2008-07-31 23:29:10.0
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
|
