I upgraded Bamboo 5.4.2 to 5.8.1.
While trying to resolve issues regarding remote agents not running. I tried instructions from this article:
After restarting several times, I can no longer make bamboo start. It gives me the attached screenshot.
err.PNG
Thanks for raising a Support issue with us. Allow me to comment publicly here for future reference.
After looking into your logs we noticed the following stack trace:
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)
What happened is that there was an invalid value for bamboo.jms.broker.client.uri
. Once we fixed this, the application was back up and running.
We've written the following KB in case other customers need more details on this:
Thank you!
Best,
Thiago Bomfim
DevTools Atlassian
Can you please create request at support.atlassian.com?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
And attach the logs.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.