How do I stop Bamboo from shutting itself down and restarting

If your Bamboo server is shutting itself down and restarting multiple times during the day, you may be experiencing problems with Bamboo's service wrapper.

Symptom

Bamboo server is restarting it self a couple of times per day.
Wrapper reported in the log JVM seems to be hung and will be terminated.
e.g.

INFO   | wrapper  | 2009/01/28 15:24:34 | Wrapper Process has not received any CPU time for 11 seconds.  Extending timeouts.
...
INFO   | jvm 1    | 2009/01/28 15:28:17 | 2009-01-28 15:28:17,299 INFO [ActiveMQ ShutdownHook] [TransportConnector] Connector vm://bamboo Stopped
INFO   | jvm 1    | 2009/01/28 15:28:17 | 2009-01-28 15:28:17,721 INFO [ActiveMQ ShutdownHook] [BrokerService] ActiveMQ JMS Message Broker (bamboo, ID:BSYTEST5-4449-1233174172549-1:0) stopped
STATUS | wrapper  | 2009/01/28 15:28:18 | <-- Wrapper Stopped

Explanation

Bamboo's service wrapper comes with a timeout that specifies the interval at which the JVM is pinged. A response is expected in that time. If the JVM is too busy, it will not respond to this ping in time.

wrapper.ping.timeout defines the timeout in seconds. 0 means that it will never time out. The default value of this setting is 30 seconds.

Solution

Increase the timeout in the wrapper's configuration. To do this,

1. Edit <Bamboo-Install>/conf/wrapper.conf.

2. Add the following line to the end of the wrapper.conf file:

   wrapper.ping.timeout=90
   

3. Restart Bamboo. If you have any elastic agents running, ensure that they are shut down before you restart the Bamboo server. If you do not shut down your elastic instances before restarting, they will continue to run and become orphaned from your Bamboo server.