Tomcat cluster config in server.xml has incorrect private address

Bug #1214531 reported by Andrew Love
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tomcat7 (Juju Charms Collection)
New
Undecided
Unassigned

Bug Description

A straight deploy of the Tomcat7 charm on a MAAS infrastructure results in the following server.xml example:

            <Receiver className="org.apache.catalina.tribes.transport.nio.NioReceiver"
                      address="192-168-56-103.clouddomain.
192.168.56.103"
                      port="4000"
                      autoBind="0"
                      selectorTimeout="5000"
                      maxThreads="6"/>

Note the address attribute. Seems to be a concatenation of hostname -A + "." + " " + IPaddress.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.