Details
-
Bug
-
Resolution: Fixed
-
Low
-
5.10.1
-
None
-
None
Description
Summary
The Windows service installation script sets heap values that are different than those defined when running from the command-line (set using setenv.bat).
Expected result
Heap is defined with these values:
setenv.bat
set JVM_MINIMUM_MEMORY=256m set JVM_MAXIMUM_MEMORY=768m
Actual result
Xms=128
Xmx=256
service.bat
"%EXECUTABLE%" //IS//%SERVICE_NAME% ^
--Description "Atlassian Bamboo Server - http://localhost:8085/" ^
--DisplayName "%DISPLAYNAME%" ^
--Install "%EXECUTABLE%" ^
--LogPath "%CATALINA_BASE%\logs" ^
--StdOutput auto ^
--StdError auto ^
--Classpath "%CLASSPATH%" ^
--Jvm "%JVM%" ^
--StartMode jvm ^
--StopMode jvm ^
--StartPath "%CATALINA_HOME%" ^
--StopPath "%CATALINA_HOME%" ^
--StartClass org.apache.catalina.startup.Bootstrap ^
--StopClass org.apache.catalina.startup.Bootstrap ^
--StartParams start ^
--StopParams stop ^
--JvmOptions "-Dcatalina.home=%CATALINA_HOME%;-Dcatalina.base=%CATALINA_BASE%;-Djava.endorsed.dirs=%CATALINA_HOME%\endorsed;-Djava.io.tmpdir=%CATALINA_BASE%\temp;-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager;-Djava.util.logging.config.file=%CATALINA_BASE%\conf\logging.properties" ^
--JvmMs 128 ^
--JvmMx 256
Attachments
Issue Links
- duplicates
-
-
- Closed
-