Bug 780030 (SOA-2392)

Summary:	default memory settings
Product:	[JBoss] JBoss Enterprise SOA Platform 5	Reporter:	Aleksandar Kostadinov <akostadinov>
Component:	Configuration	Assignee:	Julian Coleman <jcoleman>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	5.1.0.ER2	CC:	kevin.conner
Target Milestone:	---
Target Release:	5.1.0 GA, 5.1.0.ER6
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-2392
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:	32bit, maybe all
Last Closed:	2011-02-17 10:01:13 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Aleksandar Kostadinov 2010-10-07 19:28:42 UTC

Affects: Compatibility/Configuration
Steps to Reproduce: export JAVA_OPTS=""
bin/run.sh <options>
project_key: SOA

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.

Comment 1 Aleksandar Kostadinov 2010-10-07 19:29:15 UTC

Link: Added: This issue is related to SOA-2377

Comment 2 Aleksandar Kostadinov 2010-10-07 20:03:58 UTC

To be clear the issue is that current memory settings set by the scripts are not working for particular architectures *and* are too low for the clients to be running any applications. We need default settings that will be reasonable for a starter (at least server alone needs to start cleanly on all certified platforms).

Comment 4 Len DiMaggio 2010-10-28 13:38:28 UTC

Link: Added: This issue related SOA-2377

Comment 5 Anne-Louise Tangring 2010-12-02 15:48:52 UTC

PM team decided this is a blocker for SOA 5.1.0. We may not be able to make it work, in which case it will turn into a documentation issue and handed over to ECS.

Comment 6 Kevin Conner 2010-12-09 15:30:21 UTC

I made some rough comparisons as part of SOA-2377.

Comment 7 Kevin Conner 2010-12-14 19:34:13 UTC

The issue on the windows box is the amount of contiguous memory available for allocation to heap/permgen, and this seems to change depending on the particular server.

Looking at the memory map of the java process running on soa5 would suggest that the maximum available (for this machine) is 1674m.  Our current configuration is 1303m and 512m, 1815m in total.

In order to cover this variance in available memory it may be sufficient to lower the permgen to 256m.

Comment 8 Kevin Conner 2010-12-14 19:43:35 UTC

I should add that the important aspect of these settings is to allow someone to start the server without issue, we could equally choose to reduce the heap.

Comment 9 Kevin Conner 2010-12-15 11:54:29 UTC

Talked with Andy Miller and he suggested removing the -XX:MaxPermSize=512m from the server.  We still need to include the PermSize configuration as we exceed the default size.

Comment 10 Kevin Conner 2010-12-15 12:03:48 UTC

Assigning to Julian to override the run.conf/bat settings

Comment 11 Kevin Conner 2010-12-15 12:14:02 UTC

Talked this over with Julian and we appear to modify the EAP settings.  EAP appear to use "-Xms1303m -Xmx1303m -XX:MaxPermSize=256m" so we should revert to that.

Comment 12 Kevin Conner 2010-12-15 13:24:06 UTC

The QE team now specify their own startup parameters so it is safe to reduce these in the SOA configurations.

Comment 13 Julian Coleman 2010-12-15 14:49:16 UTC

Resolved with revision 7642 of:

  build-tools/builders/eap/post-patch/patch_run_bat.xml

Commit message:

  SOA-2392
  Use memory settings from EAP as default settings.

Comment 14 Laura Bailey 2010-12-17 00:41:32 UTC

Writer: Added: Darrin

Comment 15 Laura Bailey 2010-12-17 00:47:56 UTC

Release Notes Docs Status: Added: Not Yet Documented

Comment 16 Aleksandar Kostadinov 2010-12-29 19:20:10 UTC

Confirmed with ER6 that server starts up on machines with with 4G of RAM even on the supported windows.versions.

Comment 17 Dana Mison 2011-02-17 10:01:13 UTC

Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Resolved Issue
Labels: Removed: rn-dmison 
Release Notes Text: Added: 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.