Help configuring bamboo as a service in windows 10 home

[Peter Daniels]

Environment:

Windows 10 Home Edition, x64

Bamboo 6.7

Jdk1.8.0_191

I am able to run Bamboo usin a cmd shell and bin\start-bamboo.bat, but I have yet to find success configuring it to run as a windows service.  This will NOT be the prod setup - just for developing a PoC.  I have looked at the follwing pages:

https://confluence.atlassian.com/bamboo/running-bamboo-as-a-windows-service-289277308.html

https://confluence.atlassian.com/bamboo/running-bamboo-as-a-windows-service-as-the-local-user-416580754.html

When configuring the service either as "local system" or as my own user account (admin), the service starts, but am unable to connect to localhost:8085.  Can't see, to find a way to configure local sec policy on windows 10 home edition for account to "logon as service".  Is that possibly my issue?

Also note that I uninstalled (using uninstall.exe) and re-installed bamboo (atlassian-bamboo-6.7.1-windows-x64.exe) a # of times while fumbling around with the right JDK and running the server as admin in cmd shell.

TIA,

-Peter

Update: noticed this in the logs (bamboo-stderr.2018-12-02.log):

WARNING [ContainerBackgroundProcessor[StandardEngine[Catalina]]] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadDetected Thread [http-nio-8085-exec-2] (id=[214]) has been active for [61,423] milliseconds (since [12/2/18 9:16 AM]) to serve the same request for [http://localhost:8085/allPlans.action] and may be stuck (configured threshold for this StuckThreadDetectionValve is [60] seconds). There is/are [1] thread(s) in total that are monitored by this Valve and may be stuck.

[Ulrik Ekedahl · Accepted solution]

I think that this may be the same bug as I experienced in the install script of Bamboo as a Windows service. I also thought it was a security problem, but it was a memory problem. The install script allocates to little memory to the windows service, and the result is that the web server times out. 

See the bug report for a manual workaround.

[Peter Daniels]

Thank you!  That did the trick.  I uninstalled the service, edited service.bat to bump the memory config:

if "%SERVICE_STARTUP_MODE%" == "" set SERVICE_STARTUP_MODE=manual
if "%JvmMs%" == "" set JvmMs=512
if "%JvmMx%" == "" set JvmMx=1024

and started the service.  It's up.