Details
Description
Setting the cargo.hostname property to 0.0.0.0 does not make JBoss listen on all interfaces.
The work-around is to set jboss.bind.address system variable. This is however containter-specific.
<plugin>
<groupId>org.codehaus.cargo</groupId>
<artifactId>cargo-maven2-plugin</artifactId>
<version>1.2.1</version>
<configuration>
<configuration>
<properties>
<cargo.jvmargs><![CDATA[-Xdebug -Xrunjdwp:transport=dt_socket,address=5005,server=y,suspend=n]]></cargo.jvmargs>
<cargo.hostname>0.0.0.0</cargo.hostname> <!-- DOES NOT WORK -->
</properties>
</configuration>
<container>
<containerId>jboss71x</containerId>
<artifactInstaller>
<groupId>org.jboss.as</groupId>
<artifactId>jboss-as-dist</artifactId>
<version>${jboss.version}</version>
<type>zip</type>
</artifactInstaller>
<systemProperties>
<jboss.bind.address>0.0.0.0</jboss.bind.address> <!-- IT WORKS -->
</systemProperties>
</container>
<deployer>
<type>installed</type>
<deployables>
<deployable>
<groupId>${project.groupId}</groupId>
<artifactId>${project.artifactId}</artifactId>
<type>war</type>
<properties>
<context>${project.artifactId}</context>
</properties>
</deployable>
</deployables>
</deployer>
</configuration>
</plugin>
Issue Links
- relates to
-
CARGO-758
Unable to set bind address to 0.0.0.0 when starting jboss
-
Fixed revision 3330.
Please note that the CI being down, you will have to build CARGO 1.2.3-SNAPSHOT yourself to verify the fix. Details on http://cargo.codehaus.org/Building