Name: tb29552 Date: 07/31/2003
FULL PRODUCT VERSION :
java.vm.info=mixed mode
java.vm.name=Java HotSpot(TM) Server VM
java.vm.specification.name=Java Virtual Machine Specification
java.vm.specification.vendor=Sun Microsystems Inc.
java.vm.specification.version=1.0
java.vm.vendor=Sun Microsystems Inc.
java.vm.version=1.4.2-b28
FULL OS VERSION :
OS Name Microsoft Windows 2000 Server
Version 5.0.2195 Service Pack 2 Build 2195
System Manufacturer IBM
System Type X86-based PC
Processor x86 Family 6 Model 10 Stepping 1 GenuineIntel ~700 Mhz
Processor x86 Family 6 Model 10 Stepping 1 GenuineIntel ~700 Mhz
Locale United States
Total Physical Memory 2.096.648 KB
Total Virtual Memory 7.180.764 KB
Page File Space 5.084.116 KB
A DESCRIPTION OF THE PROBLEM :
The HotSpot server VM ignores the maximum heap size setting, resulting in an out of memory error.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Our VM settings are:
-server
-Xms900m
-Xmx900m
-XX:NewSize=32m
-XX:MaxNewSize=32m
-XX:SurvivorRatio=128
-XX:MaxTenuringThreshold=0
-XX:+UseConcMarkSweepGC
-XX:CMSInitiatingOccupancyFraction=60
-verbosegc
-XX:+PrintGCApplicationStoppedTime
-XX:+PrintGCTimeStamps
-XX:+PrintGCDetails
-Xloggc:F:\LOG\DT02\SYSTEM\gc.log
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
We expect the CMS collector to run when the vm reaches the heap size of 900MB.
ACTUAL -
When we run our home grown application server, we see the memory claimed by the VM raising to up to 1,317,138,432 bytes (W2K Performance Monitor/working set). But the last line of the gc-log states that only a few hundred MBs are used by the VM :
[GC [ParNew: 32639K->0K(32704K)] 312471K->287751K(921536K)]
and the OS has 138,289,152 bytes (physical memory) free.
Then the VM exits with the provided message.
I can provide the full gc-log and "W2K Performance Monitor" log if needed.
ERROR MESSAGES/STACK TRACES THAT OCCUR :
Exception in thread "CompilerThread0" java.lang.OutOfMemoryError: requested 111372 bytes for Chunk::new. Out of swap space?
At that time W2K reports 138,289,152 bytes free physical memory
REPRODUCIBILITY :
This bug can be reproduced always.
CUSTOMER SUBMITTED WORKAROUND :
When set the maximum heap size to a smaller value, so the old generation fills up to the "CMSInitiatingOccupancyFraction" of 60%, then a normal collection is done by the CMS collector.
(Review ID: 193262)
======================================================================
###@###.### 10/9/04 00:12 GMT
FULL PRODUCT VERSION :
java.vm.info=mixed mode
java.vm.name=Java HotSpot(TM) Server VM
java.vm.specification.name=Java Virtual Machine Specification
java.vm.specification.vendor=Sun Microsystems Inc.
java.vm.specification.version=1.0
java.vm.vendor=Sun Microsystems Inc.
java.vm.version=1.4.2-b28
FULL OS VERSION :
OS Name Microsoft Windows 2000 Server
Version 5.0.2195 Service Pack 2 Build 2195
System Manufacturer IBM
System Type X86-based PC
Processor x86 Family 6 Model 10 Stepping 1 GenuineIntel ~700 Mhz
Processor x86 Family 6 Model 10 Stepping 1 GenuineIntel ~700 Mhz
Locale United States
Total Physical Memory 2.096.648 KB
Total Virtual Memory 7.180.764 KB
Page File Space 5.084.116 KB
A DESCRIPTION OF THE PROBLEM :
The HotSpot server VM ignores the maximum heap size setting, resulting in an out of memory error.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Our VM settings are:
-server
-Xms900m
-Xmx900m
-XX:NewSize=32m
-XX:MaxNewSize=32m
-XX:SurvivorRatio=128
-XX:MaxTenuringThreshold=0
-XX:+UseConcMarkSweepGC
-XX:CMSInitiatingOccupancyFraction=60
-verbosegc
-XX:+PrintGCApplicationStoppedTime
-XX:+PrintGCTimeStamps
-XX:+PrintGCDetails
-Xloggc:F:\LOG\DT02\SYSTEM\gc.log
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
We expect the CMS collector to run when the vm reaches the heap size of 900MB.
ACTUAL -
When we run our home grown application server, we see the memory claimed by the VM raising to up to 1,317,138,432 bytes (W2K Performance Monitor/working set). But the last line of the gc-log states that only a few hundred MBs are used by the VM :
[GC [ParNew: 32639K->0K(32704K)] 312471K->287751K(921536K)]
and the OS has 138,289,152 bytes (physical memory) free.
Then the VM exits with the provided message.
I can provide the full gc-log and "W2K Performance Monitor" log if needed.
ERROR MESSAGES/STACK TRACES THAT OCCUR :
Exception in thread "CompilerThread0" java.lang.OutOfMemoryError: requested 111372 bytes for Chunk::new. Out of swap space?
At that time W2K reports 138,289,152 bytes free physical memory
REPRODUCIBILITY :
This bug can be reproduced always.
CUSTOMER SUBMITTED WORKAROUND :
When set the maximum heap size to a smaller value, so the old generation fills up to the "CMSInitiatingOccupancyFraction" of 60%, then a normal collection is done by the CMS collector.
(Review ID: 193262)
======================================================================
###@###.### 10/9/04 00:12 GMT
- duplicates
-
JDK-4797189 Finalizers not called promptly enough
- Closed
- relates to
-
JDK-4916142 CompilerThread0: OutOfMemoryError Chunk::new Out of swap space?
- Closed
-
JDK-4871440 memory growth of over 100m with 1.4.1_02 vs. 1.3.1
- Closed