Bug 780563 (SOA-2998)

Summary: The jvm options in run.conf.bat get ignored when using service.bat
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Mustafa Musaji <mmusaji>
Component: EAP, ConfigurationAssignee: trev <tkirby>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.1.0 GACC: mmusaji
Target Milestone: ---   
Target Release: 5.2.0 GA, 5.2.0.ER2   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-2998
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Windows only
Last Closed: 2011-11-07 13:05:17 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 Mustafa Musaji 2011-04-01 14:23:44 UTC
Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000006m1Zm&sfdc.override=1
Workaround: Workaround Exists
Workaround Description: set the JVM options one place only

(in service.bat or run.conf.bat)
project_key: SOA

If you use service.bat and have your jvm options set in run.conf.bat they will be ignored.

This happens because service.bat sets %JAVA_OPTS% by

  set JAVA_OPTS=-Xrs

later on, service.bat uses run.bat which calls run.bat.conf
in run.bat.conf there is a check to see if %JAVA_OPTS% are set -

  if not "x%JAVA_OPTS%" == "x" goto JAVA_OPTS_SET

so, if JAVA_OPTS are set it doesn't jump to :JAVA_OPTS_SET
and the script carries on and sets all the vm parameters at

  rem # JVM memory allocation pool parameters - modify as appropriate.

  set "JAVA_OPTS=-Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dsun.lang.ClassLoader.allowArraySyntax=true"

So when using service.bat these parameters get ignored.

I note that this is mentioned in https://jira.jboss.org/browse/JBNATIVE-59 and the fix for service.bat overwriting %JAVA_OPTS% is in currently in trunk.

Comment 1 Mustafa Musaji 2011-04-01 14:23:45 UTC
Link: Added: This issue Cloned from JBPAPP-5403


Comment 2 Mustafa Musaji 2011-04-01 14:26:01 UTC
Writer: Removed: elspeth 
Help Desk Ticket Reference: Removed: https://c.na7.visual.force.com/apex/Case_View?id=500A0000004SaaIIAS Added: https://c.na7.visual.force.com/apex/Case_View?id=500A0000006m1Zm&sfdc.override=1


Comment 3 Mustafa Musaji 2011-04-01 14:29:08 UTC
Release Notes Docs Status: Removed: Documented as Resolved Issue 


Comment 5 Julian Coleman 2011-04-05 13:51:01 UTC
JBPAPP-5403 is fixed for EAP 5.1.1, so SOA 5.2.0 will incorporate the fix.


Comment 6 Douglas Palmer 2011-08-11 13:40:40 UTC
Fixed in EAP 5.1.1

Comment 7 David Le Sage 2011-08-31 05:59:22 UTC
Release Notes Docs Status: Added: Documented as Resolved Issue
Writer: Added: dlesage
Release Notes Text: Removed: When starting the server using service.bat, no options were inherited from run.conf.bat. This occurred because service.bat set JAVA_OPTS to a placeholder value, which was not overridden by values set in run.conf.bat due to a faulty check. This issue has been fixed, and options set in run.conf.bat are now used when starting the server with service.bat. Added: https://issues.jboss.org/browse/SOA-2998

When starting the server using service.bat, no options were inherited from run.conf.bat. This occurred because service.bat set JAVA_OPTS to a placeholder value, which was not overridden by values set in run.conf.bat due to a faulty check. This issue has been fixed, and options set in run.conf.bat are now used when starting the server with service.bat. 


Comment 8 Aleksandar Kostadinov 2011-11-07 13:03:51 UTC
Release Notes Docs Status: Removed: Documented as Resolved Issue Added: Not Required


Comment 9 Aleksandar Kostadinov 2011-11-07 13:05:17 UTC
we do not ship service.bat with SOA-P so it is not applicable and release notes are not required