You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@servicemix.apache.org by "Alexander Sahler (JIRA)" <ji...@apache.org> on 2014/12/11 08:48:12 UTC

[jira] [Created] (SM-2410) windows startup scripts don't handle setenv.bat correctly

Alexander Sahler created SM-2410:
------------------------------------

             Summary: windows startup scripts don't handle setenv.bat correctly
                 Key: SM-2410
                 URL: https://issues.apache.org/jira/browse/SM-2410
             Project: ServiceMix
          Issue Type: Bug
    Affects Versions: 5.3.0
         Environment: Windows Any
            Reporter: Alexander Sahler


When setting variables in setenv.bat they don't find their way to JAVA_DEFAULT_OPTIONS. This is due to the variable overwrite in line 231.
{noformat}
set DEFAULT_JAVA_OPTS=%JAVA_MODE% -Xms%JAVA_MIN_MEM% -Xmx%JAVA_MAX_MEM% -Dderby.system.home="%KARAF_DATA%\derby" -Dderby.storage.fileSyncTransactionLog=true -Dcom.sun.management.jmxremote -XX:+UnlockDiagnosticVMOptions -XX:+UnsyncloadClass
{noformat}

Instead it should be:
{noformat}
set DEFAULT_JAVA_OPTS=%JAVA_MODE% %DEFAULT_JAVA_OPTS% -Xms%JAVA_MIN_MEM% -Xmx%JAVA_MAX_MEM% -Dderby.system.home="%KARAF_DATA%\derby" -Dderby.storage.fileSyncTransactionLog=true -Dcom.sun.management.jmxremote -XX:+UnlockDiagnosticVMOptions -XX:+UnsyncloadClass
{noformat}
to keep the previous contents of DEFAULT_JAVA_OPTS.

The same applies for karaf.bat.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)