-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Blocker
-
Resolution: Done
-
Affects Version/s: 5.1.0.ER2
-
Component/s: Configuration
-
Labels:None
-
Environment:
32bit, maybe all
-
Steps to Reproduce:
-
Affects:Compatibility/Configuration
-
Release Notes Text:The default JVM memory settings in run.conf (and run.conf.bat) have been updated in this release. PermSize is no longer set, and MaxPermSize is set to 256 megabytes. This provides a more consistent server behavior on different platforms.
-
Release Notes Docs Status:Documented as Resolved Issue
Currently run.sh/bat seems to be setting memory settings for all available configurations:
-Xms1303m -Xmx1303m -XX:PermSize=256m -XX:MaxPermSize=512m
This doesn't work in my tests (see below).
Windows 32bit (tried on w2k3 and w2k8 with 4GB of physical memory):
Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine.
solaris sparc(64):
For some reason I'm seeing OutOfMemoryError permgen and other I think caused by that errors so server doesn't start. Jiri Pechanec reported that with "-Xmx1500m -XX:MaxPermSize=1024m" server starts normally on the machines I have tested on.
All architectures:
- Martin reported that SOA-P production server occupies around 1,2G with no applications deployed (Martin could you provide a link to the jprofile report?). So 1303m seems to me too low for a server + any user application.
- On the other hand I'm not sure why window 32bit can't allocate 1,3G of memory... perhaps things would work if lower limit is NOT set?
- Just a side note that our solaris 9/10 x86(_64) and solaris9 sparc hardware have only 2GB of physical memory so I am not able to definitely say there is no problem there.
