WildFly System Properties: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 40: | Line 40: | ||
=jboss.bind.address= | =jboss.bind.address= | ||
Represents the value of the instance's public interface. | |||
One common method of externalizing this operationally is to define it as a system property at the bottom of <tt>standalone.conf</tt>: | |||
<pre> | |||
... | |||
JAVA_HOME="${JAVA_HOME} -Djboss.bind.address=192.168.1.15" | |||
</pre> | |||
=jboss.bind.address.management= | =jboss.bind.address.management= | ||
Revision as of 01:29, 12 February 2016
Internal
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.server.config.dir
Used by:
jboss.bind.address
Represents the value of the instance's public interface.
One common method of externalizing this operationally is to define it as a system property at the bottom of standalone.conf:
...
JAVA_HOME="${JAVA_HOME} -Djboss.bind.address=192.168.1.15"