Subordinate WildFly Host Controller Post-Install Configuration: Difference between revisions
| Line 54: | Line 54: | ||
</pre> | </pre> | ||
=The Host Controller's Management Interface= | |||
A subordinate host controller does not need to expose its management interface. | |||
A subordinate host controller does not need to expose its management interface. | |||
For more details see [[WildFly System Properties#jboss.domain.master.address]] and [[WildFly System Properties#jboss.domain.master.port]]. | For more details see [[WildFly System Properties#jboss.domain.master.address]] and [[WildFly System Properties#jboss.domain.master.port]]. | ||
=Specify the Domain Controller= | =Specify the Domain Controller= | ||
Revision as of 05:47, 12 February 2016
Internal
Overview
This procedure is part of WildFly Unzip Installation. Once completed, return to WildFly Unzip Installation to continue the post-install procedure.
host.xml Host Name
A subordinate host controller uses its host name as username when authenticating against the Management Realm of the domain controller, so the host name it is configured with is important. The host name can be hardcoded in host.xml or specified as a system property. For more details see:
Specify the Master Domain Controller
Modify $JBOSS_HOME/domain/configuration/host.xml as follows:
...
<domain-controller>
<remote host="1.2.3.4" port="${jboss.domain.master.port:9999}" security-realm="ManagementRealm"/>
</domain-controller>
...
Note that the management functionality can be exposed over 9999 or 9990.
It is possible to expose the master domain controller address externally as 'jboss.domain.master.address' system property. In this case, you'd have to add the following to domain.conf:
HOST_CONTROLLER_JAVA_OPTS="${HOST_CONTROLLER_JAVA_OPTS} -Djboss.domain.master.address=1.2.3.4"
However, this is NOT a good idea. If we go through a domain controller failover, promotion and unpromotion, the IP address will be written into the host.xml file directly, so the 'jboss.domain.master.address' will lose its usefulness and it will suddenly become confusing - we used a system property but also we have hardcode in the file.
For more details on jboss.domain.master.address see:
Connection Failure Symptoms
In $JBOSS_HOME/domain/log/host-controller.log:
22:36:16,823 WARN [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010900: Could not connect to remote domain controller at remote://10.155.78.202:9999 -- java.net.ConnectException: JBAS012174: Could not connect to remote://10.155.78.202:9999. The connection failed 22:36:16,828 WARN [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010900: Could not connect to remote domain controller at remote://10.155.78.202:9999 -- java.lang.IllegalStateException: JBAS010951: Could not connect to master in 11 attempts within 30000 ms 22:36:16,828 WARN [org.jboss.as.host.controller] (Controller Boot Thread) JBAS016581: No domain controller discovery options remain. 22:36:16,829 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010901: Could not connect to master. Aborting. Error was: java.lang.IllegalStateException: JBAS016519: Tried all domain controller discovery option(s) but unable to connect
The Host Controller's Management Interface
A subordinate host controller does not need to expose its management interface.
For more details see WildFly System Properties#jboss.domain.master.address and WildFly System Properties#jboss.domain.master.port.