This documentation relates to an earlier version of Bamboo.
View

Unknown macro: {spacejump}

or visit the current documentation home.

(info) These instructions apply to the Bamboo distribution (not EAR-WAR), which ships with the Jetty application server.

 
If you have installed Bamboo on a machine with multiple interfaces, and need to bind Bamboo to a single IP address, follow these instructions.

Step 1 — Instruct Bamboo to read its configuration from the jetty.xml file

By default Bamboo doesn't use the jetty.xml file to configure itself. You will need to tell Bamboo to use it.

Step 2 — Edit the Jetty.xml file 

Your jetty.xml file is located in <Bamboo_Install_directory>/webapp/WEB-INF/classes/jetty.xml.
Please note: YOUR_HOST_URL should be the same as the Bamboo base URL configured in Bamboo.

If you are using Bamboo 1.2.4:

Find the following section:

<Call name="addListener">
        <Arg>
            <New class="org.mortbay.http.SocketListener">
                <Set name="Port">
                    <SystemProperty name="jetty.port" default="8085"/>
                </Set>
                <Set name="Host">127.0.0.1</Set>

Change the last line as follows:

<Call name="addListener">
        <Arg>
            <New class="org.mortbay.http.SocketListener">
                <Set name="Port">
                    <SystemProperty name="jetty.port" default="8085"/>
                </Set>
                <Set name="Host">YOUR_HOST_URL</Set>

 

If you are using Bamboo 2.0

Find the following section:

 <Call name="addConnector">
    <Arg>
      <New class="org.mortbay.jetty.bio.SocketConnector">
        <Set name="Port">
          <SystemProperty name="jetty.port" default="8085"/>
        </Set>
        <!--<Set name="Host">127.0.0.1</Set>-->

Uncomment the host property as follows:

 <Call name="addConnector">
    <Arg>
      <New class="org.mortbay.jetty.bio.SocketConnector">
        <Set name="Port">
          <SystemProperty name="jetty.port" default="8085"/>
        </Set>
        <Set name="Host">YOUR_HOST_URL</Set>

 

Step 3 — Restart Bamboo

If you have any elastic agents running, ensure that they are shut down before you restart the Bamboo server. If you do not shut down your elastic instances before restarting, they will continue to run and become orphaned from your Bamboo server.

  • ラベルなし

5 Comments

  1. Anonymous

    This will not work for 3.1 anymore. jetty.xml format has changed and addConnector directives are simply ignored by the wrapper. Please update this page with working instructions.

  2. Test Test

    I will second what Anonymous has to say.  This does not work for Bamboo 3.2.x, either.

    1. Anonymous

      Look further down in jetty.xml

      This property                     <SystemProperty name="bamboo.webapp" default="./webapp"/>

      Relative to the wrapper.conf, webapp is at ../webapp/, not ./webapp.  Changing this worked for me.  Perhaps setting bamboo.webapp would be a better practice, but I'm not sure where the "proper" place to do that would be.

       

  3. Anonymous

    Please update this page with working instructions for 3.2.x. I do not want Bamboo listening on an external ip!

  4. SharlatanY

    Use a connector tag like the following, it works for me:

    <Call name="addConnector">
     <Arg>
      <New class="org.eclipse.jetty.server.nio.SelectChannelConnector">
       <Set name="host"><Property name="jetty.host" default="192.168.15.19"/></Set>
       <Set name="port"><Property name="jetty.port" default="80"/></Set>
       <!--<Set name="ConfidentialPort">8443</Set>-->
       <!--<Set name="IntegralPort">8443</Set>-->
      </New>
     </Arg>
    </Call>

     

    I think the main thing is to change "org.mortbay.http.SocketListener" to "org.eclipse.jetty.server.nio.SelectChannelConnector".