We're updating the issue view to help you get more done. 

Unable to set bind address to 0.0.0.0 when starting JBoss 7.1.x

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.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 <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>

Status

Assignee

Savas Ali Tokmen

Reporter

Damian Nowak

Components

Fix versions

Affects versions

1.2.2

Priority

Major