JDK : 1.5.0-b32 (passed on b31)
VM : client/server
switch/Mode : -XX:+UseParallelGC (passed without this switch)
Platform[s] : Windows XP
Test owner :
Failing Test :
  nsk/stress/except/except004

TestBase Location:
==================
    /net/sqesvr-nfs/global/nfs/test_results4/VM/UNIFIED-DTF/DTWS/suites/VM_FULLLOOK/testbase/

Test source location:
=====================
/net/sqesvr-nfs/global/nfs/test_results4/VM/UNIFIED-DTF/DTWS/suites/VM_FULLLOOK/testbase/src/nsk/stress/except/except004/*.java

Share source location:
======================
/net/sqesvr-nfs/global/nfs/test_results4/VM/UNIFIED-DTF/DTWS/suites/VM_FULLLOOK/testbase/src/nsk/logging/share/*

tlog file location:
==================
/java/sqa/st4/VM/tiger/DTWS/results/1.5.0-beta-b32/ServerVM/WIN/mixed/VM/GC_FULL
LOOK-19-WEEKLY-VM-ServerVM-mixed-WIN-en-2004-01-06-14-03-12-0531/ResultDir/except004

How to reproduce:
====================

   1. map x: to //sm-usca19-01/net/jano.sfbay
   2. cp x:/export/disk20/GammaBase/Bugs/{this_bug_number}/* to your local dir.
   3. map y: to //cady.sfbay/export
   4. sh
   5. myrerun.sh [your jdk] [-client | -server] [-XX:+UseParallelGC]
   6. echo $?

Test output:
=============
##Exit status of execution step=96
##!checkExitCode

## While printing this message, JVM seems to initiate the output
## stream, so that it will not need more memory to print later,
## when the heap would fail to provide more memory.
##
## Note, that the test maintains especial static log[] field in
## order to avoid printing when the heap seems exhausted.
## Nevertheless, printing could arise OutOfMemoryError even
## after all the memory allocated by the test is released.
##
## That problem is caused by the known JDK/HotSpot bugs:
## 4239841 (P1/S5) 1.1: poor garbage collector performance
## 4245060 (P4/S5) poor garbage collector performance
##
## This message is just intended to work-around that problem.
## If printing should fail even so, the test will return the
## exit status 96 instead of 97 to indicate the problem.


Specific Machine Info:
=====================
Windows_NT VMNIGHTLY10 5 01 586
 




###@###.### 2004-01-09


*************
Following tests may also have same failures.

nsk/sysdict/vm/stress/chain/chain005
nsk/sysdict/vm/stress/chain/chain007
nsk/sysdict/vm/stress/chain/chain008

###@###.### 2004-01-09

The following test maybe test bug:
nsk/sysdict/vm/stress/btree/btree007

reproduced in b37
###@###.### 2/9/04