I followed the instructions on this page:
To get bamboo proxied behind an Apache HTTP server. I've configured Apache appropriately (using it for our other servers) and modified the conf/wrapper.conf file as specified in the documentation. However, when I call wrapper/start-bamboo start and tail the logs/bamboo.log, I get the following exception:
Loading jetty configuration file 'webapp/WEB-INF/classes/jetty.xml' from the classpath as it does not exist on the filesystem.
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at java.lang.Thread.run(Unknown Source)
If I change everything back to standard, it works as expected.
Check the wrapper.conf file again. I use the same setup (reverse proxying with apache httpd) and my wrapper.conf has these initial lines :
Make sure you comment out any other lines with "wrapper.app.parameter.X" as the PORT, PATH to the jetty file, and Content (/) get specified in the jetty XML. and that the numbers are sequential.
Additionally double-check how you're starting Bamboo. If you use the bamboo.sh file, has it been modified or moved? It includes the wrapper.conf info using :
where $BAMBOO_INSTALL is built from the directory of the bamboo.sh file. If that file gets moved it can affect the env variables and the wrapper.conf file cannot resolve the path webapp/WEB-INF/classes/jetty.xml correctly.
If your HTTPD reverse proxy is serving via SSL, in the jetty.xml make sure to include :
<Set name="host"><Property name="jetty.host" /></Set>
<Set name="port"><Property name="jetty.port" default="8443"/></Set>
<Set name="Keystore"><SystemProperty name="jetty.home" default="."/>/ssl/keystore</Set>
You need to generate a local keystore on the bamboo server and inside it generate a self-signed cert with password and keypass that you define in the addConnector XML above (replace KEYPASS with your password). This seems to be necessary to get Bamboo to listen on an SSL port and then you update your Apache conf file to proxypass an dproxypassreverse to the bamboo SSL port. If you don't then Bamboo breaks in the SSL reverse proxy config.
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot