Documentation for Bamboo 4.2.x. Documentation for other versions of Bamboo is available too.

The Bamboo start up script can be customised to setup JNDI resources

Follow this guide to setup Bamboo to use the jetty.xml file

You will also need to change the jetty.xml file under webapp/WEB-INF/classes by change the context path from /bamboo to /. Example of this is below:

If you are using Bamboo 1.2.4 (or earlier):

<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<!-- Add root context web applications. -->
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<Call name="addWebApplication">
    <Arg>/</Arg>
    <Arg>
       <SystemProperty name="bamboo.webapp" default="webapp"/>
    </Arg>
</Call>


If you are using Bamboo 2.0:

<Call name="addHandler">
    <Arg>
       <New class="org.mortbay.jetty.webapp.WebAppContext">
          <Arg name="webApp">
            <SystemProperty name="bamboo.webapp" default="webapp"/>
          </Arg>
          <Arg name="contextPath">
            /
          </Arg>
        </New>
      </Arg>
</Call>


To set up the JNDI mail session, you will also need to uncomment and modify the section of this jetty.xml shown below. You will need to replace the values inside the <Arg> tags with appropriate values (username, password, host, from address).


In Bamboo 1.2.4 and earlier:

<!--
    <Call name="addService">
        <Arg>
            ...
        </Arg>
    </Call>
-->

In Bamboo 2.0:

 <!--
<New id="resourceID" class="org.mortbay.jetty.plus.naming.Resource">
    <Arg>resourceName</Arg>
    <Arg>
      <New class="org.mortbay.naming.factories.MailSessionReference">
            ...
      </New>
    </Arg>
 </New>
-->

If you are experiencing class loading problems with your mail session. Try uncommenting the following line in the web applications context (2.0 only):

<!--<Set name="parentLoaderPriority">true</Set>-->
  • No labels


Log a request with our support team.


Raise an issue for our developers or tech writers.


See answers from the community.


Tweet, blog and update our documentation.

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.