FULL PRODUCT VERSION :
java version "1.5.0_03"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_03-b07)
Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_03-b07, mixed mode)

ADDITIONAL OS VERSION INFORMATION :
Linux crawling015.archive.org 2.6.11-1.1369_FC4smp #1 SMP Thu Jun 2 23:16:33 EDT 2005 x86_64 x86_64 x86_64 GNU/Linux


A DESCRIPTION OF THE PROBLEM :
Any GC system with 'ergonomics' (ParallelGC, and apparently CMS in 1.6) can throw OutOfMemoryError even when there's plenty of heap space left, but GC has been taking 'too much' time. These errors, however, include the misleading explanation string "java heap space". They should instead say something like 'ergonomics GC time limits exceeded' instead, so that people receiving the error know what's really happened.

The OOM errors in all of these bugs appear due to ergonomics, remediable via the undocumented -XX:-UseGCTimeLimit JVM flag, but may have confused those experiencing the problem because they report as "java.lang.OutOfMemoryError: Java heap space".

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Run one of the memory-exhaustion-type tests in the above-referenced bugs.

EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
OutOfMemoryError that is thrown mentions true cause, ergonomics timeout, rather than "Java heap space"
ACTUAL -
java.lang.OutOfMemoryError: Java heap space

ERROR MESSAGES/STACK TRACES THAT OCCUR :
java.lang.OutOfMemoryError: Java heap space

REPRODUCIBILITY :
This bug can be reproduced always.

CUSTOMER SUBMITTED WORKAROUND :
Read lots of bugs to understand the real reason for the OOMs. Use the secret -XX:-UseGCTimeLimit JVM flag.
###@###.### 2005-06-20 06:49:38 GMT