Hide Forgot
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.
Link: Added: This issue Cloned from JBPAPP-5403
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
Release Notes Docs Status: Removed: Documented as Resolved Issue
JBPAPP-5403 is fixed for EAP 5.1.1, so SOA 5.2.0 will incorporate the fix.
Fixed in EAP 5.1.1
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.
Release Notes Docs Status: Removed: Documented as Resolved Issue Added: Not Required
we do not ship service.bat with SOA-P so it is not applicable and release notes are not required