All Versions
Bamboo 5.13Bamboo 5.7.x
Bamboo 5.6.x
More...
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.
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
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.
Increase the timeout in the wrapper's configuration. To do this,
<Bamboo-Install>/conf/wrapper.conf
.wrapper.conf
file:
wrapper.ping.timeout=90