You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I have configured Bamboo with a self signed certificate according to the online instructions. If I run Bamboo using start-bamboo.bat then it works perfectly. However if I try to use it by running the windows service I get no response. I have configured the windows service to run as the same windows user I'm using to run from the command line, as well as uninstalling and reinstalling the windows service, but this doesn't help. What should I do to resolve this?
Check the windows system log. You should find a detailed error message why windows could not start the service. Google that error message and the resolution should be straight forward.
In that case you need to check the bamboo log file. If there are no exceptions in the bamboo log, you are probably hitting an incorrect URL.
Hint: Bamboo url should be present in the startup logs.
If the log shows a failure while starting up as a service but not when starting from the command line, you java installation is corrupt (probably multiple installs of jdk and jre or 64bit vs 32 bit or the service might be püointing towards the incorrect jre- find and run
tomcat8w //ES//<ServiceName here>
to check the jvm used by the service and compare it with the jvm used from the command line. ). Verify and clean up your system variables -JDK*/JRE*/JAVA*.
Java seems to be ok - I can't see anything in the logs that would indicate any start up errors. When I try to access it, it seems to have a stuck thread:
WARNING [ContainerBackgroundProcessor[StandardEngine[Catalina]]] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadDetected Thread [https-openssl-nio-8443-exec-21] (id=) has been active for [66,162] milliseconds (since [11/26/18 3:01 PM]) to serve the same request for [REDACTED] and may be stuck (configured threshold for this StuckThreadDetectionValve is  seconds). There is/are  thread(s) in total that are monitored by this Valve and may be stuck.