-
Bug
-
Resolution: Done
-
Major
-
7.2.4.GA
-
-
-
-
-
-
+
-
Workaround Exists
-
-
Install JBoss on two different machines, add an 'admin' user and start the host-master.xml configurations on each node, like:
machineA: (10.10.10.1)
$JBOSS_HOME/bin/add-user.sh -u admin -p admin $JBOSS_HOME/bin/domain.sh --host-config.xml -Djboss.bind.address.management=10.10.10.1
machineB: 10.10.10.2
$JBOSS_HOME/bin/add-user.sh -u admin -p admin $JBOSS_HOME/bin/domain.sh --host-config.xml -Djboss.bind.address.management=10.10.10.2
And then applying a simplified script like below to machineB:
batch /host=master:write-attribute(name=name, value=slave) /host=master/core-service=discovery-options/static-discovery=primary:add(host=10.10.10.1, port=9990, protocol=remote+http) /host=master:write-remote-domain-controller(username=admin, security-realm="ManagementRealm") /host=master/core-service=management/security-realm=ManagementRealm/server-identity=secret:add(value="YWRtaW4=") run-batch /host=master:reload
Executing this scripts results in a server log output like below and stopping of the 'DomainController':
[Host Controller] INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0003: Creating http management service using network interface (management) port (9990) securePort (-1) [Host Controller] WARN [org.jboss.as.domain.management.security] (MSC service thread 1-2) WFLYDM0111: Keystore /jboss/jboss-eap-7.2/domain/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost [Host Controller] WARN [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0001: Could not connect to remote domain controller remote+http://10.0.0.1:9990: 2-$-WFLYDC0015: There is already a registered host named 'master' [Host Controller] at org.jboss.as.host.controller.RemoteDomainConnection$HostControllerConnectRequest.handleRequest(RemoteDomainConnection.java:390) [Host Controller] at org.jboss.as.protocol.mgmt.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:321) [Host Controller] at org.jboss.as.protocol.mgmt.AbstractMessageHandler.handleRequest(AbstractMessageHandler.java:286) [Host Controller] at org.jboss.as.protocol.mgmt.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:234) [Host Controller] at org.jboss.as.protocol.mgmt.ManagementChannelReceiver.handleMessage(ManagementChannelReceiver.java:85) [Host Controller] at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData(RemoteConnectionChannel.java:430) [Host Controller] at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute(EndpointImpl.java:991) [Host Controller] at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) [Host Controller] at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) [Host Controller] at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) [Host Controller] at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) [Host Controller] at java.lang.Thread.run(Thread.java:748) [Host Controller] [Host Controller] WARN [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0147: No domain controller discovery options remain. [Host Controller] ERROR [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0002: Could not connect to master. Error was: java.lang.IllegalStateException: WFLYHC0120: Tried all domain controller discovery option(s) but unable to connect [Host Controller] FATAL [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0178: Aborting with exit code 99 [Host Controller] INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0050: JBoss EAP 7.2.4.GA (WildFly Core 6.0.16.Final-redhat-00002) stopped in 77ms
- clones
-
-
- Closed
-
- is cloned by
-
-
- Closed
-
- is incorporated by
-
JBEAP-18775 (7.3.z) Upgrade WildFly Core to 10.1.4.Final-redhat-00001
-
- Closed
-
