Details

Description

JBoss AS allows configuration of service binding sets to allow running multiple instances on the same machine. This may be achieved by adding a system property for the container "-Djboss.service.binding.set=ports-01". This (in the DEFAULT configuration) shifts all ports by 100, e.g. the default HTTP connector (8080) is now available via port 8180:

<!-- The ports-01 bindings are obtained by taking the base bindings and adding 100 to each port value -->
<bean name="Ports01Bindings" class="org.jboss.services.binding.impl.ServiceBindingSet">
<constructor>
<!-- The name of the set -->
<parameter>ports-01</parameter>
<!-- Default host name -->
<parameter>${jboss.bind.address}</parameter>
<!-- The port offset -->
<parameter>100</parameter>
<!-- Set of bindings to which the "offset by X" approach can't be applied -->
<parameter><null/></parameter>
</constructor>
</bean>

This currently conflicts with the way how Cargo checking the container for being started by constructing a URL using the property "cargo.servlet.port" which defaults to 8080. Setting the property (e.g. to 8180) causes JBoss to shift again and change the port (to 8280).