-
Bug
-
Resolution: Fixed
-
P3
-
1.3.0
-
kestrel
-
x86
-
windows_nt
-
Not verified
Name: icC57033 Date: 10/28/99
JVMPI_EVENT_MONITOR_DUMP event can return wrong value for number of
threads waiting to be notified in dump buffer.
This problem prevents the VM from passing the test:
src/nsk/jvmpi/RequestEvent/reqevent001
which could be found in the HotSpot's testbase:
/net/sqesvr/vsn/testbase/testbase_nsk
or /net/sqesvr/vsn/users/NSK/ws/testbase_nsk
$ java -classic -version
java version "1.3.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0-L)
Classic VM (build 1.3.0-L, native threads, nojit)
Tests calls RequestEvent() for event JVMPI_EVENT_MONITOR_DUMP
and after receiveing JVMPI_EVENT_MONITOR_DUMP event just prints type
of monitor, number of threads waiting to enter and number of
threads waiting to be notified.
in loop for all objects in dump buffer.
Output from WinNT 4.0 environment:
JVMPI_MONITOR_JAVA, entry_count=0
number of threads waiting to enter=0
number of threads waiting to be notified=16777216
======================================================================