WildFly System Properties

Internal

• JBoss

jboss.qualified.host.name

Relevance: WildFly 9

For a host named "ap1.modcluster.local" it is set to "ap1.modcluster.local"

jboss.host.name

Relevance: WildFly 9

For a host named "ap1.modcluster.local" it is set to "ap1"

jboss.server.name

Relevance: WildFly 9

For a host named "ap1.modcluster.local" it is set to "ap1"

jboss.node.name

Relevance: WildFly 9

jboss.node.name 

Set externally with -Djboss.node.name in the startup script.

Related:

• 'jboss.node.name' in mod_cluster Concepts
• 'jboss.node.name' and the JBoss startup script

jboss.server.config.dir

Used by:

• Management API Configuration

jboss.bind.address

Represents the value of the instance's public interface. The default value is 127.0.0.1.

jboss.bind.address for Standalone Node

One common method of externalizing this operationally is to define it as a system property at the bottom of $JBOSS_HOME/bin/standalone.conf:

...
JAVA_HOME="${JAVA_HOME} -Djboss.bind.address=192.168.1.15"

The same result can be achieved by specifying the system property as a -D argument for the start script:

./standalone.sh -Djboss.bind.address=192.168.1.10

jboss.bind.address for Host Controller

One common method to externalize the value operationally for host controllers is to define it as a system property at the bottom of $JBOSS_HOME/bin/domain.conf as follows:

...
HOST_CONTROLLER_JAVA_OPTS="${HOST_CONTROLLER_JAVA_OPTS} -Djboss.bind.address=1.2.3.4"

The value propagates as system property to the process controller, host controller and servers:

eap 13556 13457 java -D[Process Controller] ... -Djboss.bind.address=1.2.3.4 ...
eap 13595 13556 java -D[Host Controller] ... -Djboss.bind.address=1.2.3.4 ...
eap 13750 13556 /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.79.x86_64/jre/bin/java -D[Server:ri2] ... -Djboss.bind.address=1.2.3.4 ...

In consequence, servers bind their HTTP connectors to that address.

jboss.bind.address.unsecure

The value to bind the "unsecure" interface to. By default 127.0.0.1.