Details
-
Bug
-
Resolution: Done
-
Major
-
EAP_EWP 5.1.0
-
None
-
Windows only
-
Workaround Exists
-
-
-
Documented as Resolved Issue
Description
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.