|
Quick Lists
|
|
Bug ID:
|
5018995
|
|
Votes
|
0
|
|
Synopsis
|
atg OOM on jtg-linux13 with tiger b43
|
|
Category
|
hotspot:garbage_collector
|
|
Reported Against
|
tiger-beta2
|
|
Release Fixed
|
|
|
State
|
11-Closed, duplicate of 4970650,
bug
|
|
Priority:
|
3-Medium
|
|
Related Bugs
|
4970650
|
|
Submit Date
|
23-MAR-2004
|
|
Description
|
with tiger b43, customer 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 customer to 6.2. This is the first time CMS is exercised with
the updated version of customer .
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
xxxxx@xxxxx 2004-03-23
|
|
Work Around
|
N/A
|
|
Evaluation
|
N/A
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
 |