After editing bamboo.cfg.xml Bamboo won't start up
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Platform Notice: Server, Data Center, and Cloud By Request - This article was written for the Atlassian server and data center platforms but may also be useful for Atlassian Cloud customers. If completing instructions in this article would help you, please contact Atlassian Support and mention it.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
After making changes to bamboo.cfg.xml and restarting Bamboo, you won't be able to log in and UI will show the following:
The following stack trace appears in the atlassian-bamboo.log:
2015-05-16 14:37:52,756 FATAL [localhost-startStop-1] [BootstrapLoaderListener] An error was encountered while bootstrapping Bamboo (see below):
null
java.lang.NullPointerException
at java.net.URLEncoder.encode(URLEncoder.java:205)
at org.apache.activemq.util.URISupport.createQueryString(URISupport.java:505)
at com.atlassian.bamboo.setup.BrokerURIUtils.reconstructCompositeUri(BrokerURIUtils.java:270)
at com.atlassian.bamboo.setup.BrokerURIUtils.decorateBrokerURI(BrokerURIUtils.java:216)
at com.atlassian.bamboo.setup.DefaultBootstrapManager.getBrokerClientURI(DefaultBootstrapManager.java:239)
at com.atlassian.bamboo.setup.DefaultBootstrapManager.afterConfigurationLoaded(DefaultBootstrapManager.java:102)
at com.atlassian.config.bootstrap.DefaultAtlassianBootstrapManager.init(DefaultAtlassianBootstrapManager.java:71)
at com.atlassian.bamboo.setup.BootstrapLoaderListener.contextInitialized(BootstrapLoaderListener.java:95)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4887)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5381)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:724)
Cause
The stack trace above means that you've configured an incorrect value for the bamboo.jms.broker.client.uri parameter below on your bamboo.cfg.xml:
<property name="bamboo.jms.broker.client.uri">failover:(tcp://abcd.testcompany.com/bamboo:54671?wireFormat.maxInactivityDuration=300000)?initialReconnectDelay=15000&maxReconnectAttempts=10</property>
Resolution
- Stop your Bamboo instance and use one of the methods below to restore this parameter:
- If you made a backup of your
bamboo.cfg.xmlprior to editing, we suggest you restore your previous configuration in order to get your Bamboo instance up and running. - If you don't have a backup, you could inspect your remote agents' old logs: they should contain the right value you had previously configured for the parameter
- If you made a backup of your
- Whatever way you chose to configure this parameter correctly, restart your application to get it up and running.