-
Bug
-
Resolution: Fixed
-
P5
-
6
-
b49
-
sparc
-
solaris
Unexpected block count failure in the following test:
sun/management/snmp/jvmThreading/JvmThreadingTest.sh
The unexpected block count is comming from the following
call in the above testcase.
ThreadMXBean.getThreadCpuTime()
The unexpected block count may be due to the internal
monitor enter.
We need to investigate this further. If the extra block
count is not unexpected then we need to fix the testcase.
One way we can fix the test case is call the getThreadCpuTime()
from a main thread instead of in the current waitingThread.
That will fix the unexpected block count error.
The reproducible test case is attached to this bug.
This problem is seen once in 500 or 1000 runs. Not
consistently reproducible.
###@###.### 2005-2-11 23:35:30 GMT
###@###.### 2005-2-11 23:43:00 GMT
###@###.### 2005-2-16 01:15:48 GMT
sun/management/snmp/jvmThreading/JvmThreadingTest.sh
The unexpected block count is comming from the following
call in the above testcase.
ThreadMXBean.getThreadCpuTime()
The unexpected block count may be due to the internal
monitor enter.
We need to investigate this further. If the extra block
count is not unexpected then we need to fix the testcase.
One way we can fix the test case is call the getThreadCpuTime()
from a main thread instead of in the current waitingThread.
That will fix the unexpected block count error.
The reproducible test case is attached to this bug.
This problem is seen once in 500 or 1000 runs. Not
consistently reproducible.
###@###.### 2005-2-11 23:35:30 GMT
###@###.### 2005-2-11 23:43:00 GMT
###@###.### 2005-2-16 01:15:48 GMT