United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: 6979312 1.5.0_24 heap generation size calculation problem
6979312 : 1.5.0_24 heap generation size calculation problem

Details
Type:
Bug
Submit Date:
2010-08-23
Status:
Closed
Updated Date:
2011-07-19
Project Name:
JDK
Resolved Date:
2010-11-11
Component:
hotspot
OS:
solaris,solaris_7
Sub-Component:
gc
CPU:
sparc
Priority:
P2
Resolution:
Fixed
Affected Versions:
5.0u24,6u13
Fixed Versions:
5.0u26-rev

Related Reports
Backport:
JDK-2201952 - 1.5.0_24 heap generation size calculation problem
Duplicate:
JDK-6822429 - configuration anomaly in JRE 6 wrt NewSize parameter: JVM refuses to start

Sub Tasks

Description
It seems that with 1.5.0_24 (not on 6uXX) there is a heap generation size calculation issue with either of the following commands.

java -Xmx2048m -Xms2048m -XX:PermSize=512m -XX:NewSize=400m -version
java -Xmx2048m -Xms2048m -XX:PermSize=512m -XX:NewSize=400m -XX:MaxNewSize=800m  -version

Error output:
Error occurred during initialization of VM
Could not reserve enough space for object heap

Strangely, this command works fine:
java -Xmx2048m -Xms2048m -XX:PermSize=512m -XX:NewSize=400m -XX:MaxNewSize=400m  -version

All three commands work in JDK 6.   It seems that in 1.5.0_24 it cannot handle a MaxNewSize bigger than NewSize? 

See comments.

Comments
EVALUATION

There are two problems in 5.0; first, it does not honour the MaxHeapSize parameter and second, it does not take care of the case when initial heap size is set equal to max heap size.
2010-10-06


Hardware and Software, Engineered to Work Together