JDK-5018995 : atg OOM on jtg-linux13 with tiger b43
  • Type: Bug
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 5.0
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: linux_redhat_9.0
  • CPU: x86
  • Submitted: 2004-03-23
  • Updated: 2004-04-05
  • Resolved: 2004-04-05
Related Reports
Duplicate :  
Description
with tiger b43, atg OOM on jtg-linux13.sfbay using CMS collector after 8 hours.

			ParallelGC	CMS GC		   SerialGC(default)
results matrix:        runs/default heap  OOM(8 hours)	   runs/default heap
length of test run	24 hours	   8 hours		3 days

I did not explicitly set the heap size in the test script.

I recently upgraded atg to 6.2. This is the first time CMS is exercised with
the updated version of atg. 

I am currently testing parallel GC with the updated version of atg6.2. After
the test completes, I will test previous J2SE build to find out if the problem
is a regression.

The logs on jtg-linux13.sfbay:
Parallel GC: /bt/atgrun.12109.-server
Default GC:  /bt/atgrun.6730.-server
CMS GC:      /bt/atgrun.25346.-server

Logs will be saved under /net/jtgb4u4c.sfbay/export/sail12/bigapps_log/Linux/tiger_b43/jtg-linux13

###@###.### 2004-03-23

Comments
PUBLIC COMMENTS The problem happened on RHEL3 and Redhat 9, but not on RHEL3 SP1. It's a kernel bug in RedHat OS (a race between cond_broadcast/signal and cond_wait )
10-06-2004