]
Rostislav Svoboda updated AS7-1816:
-----------------------------------
Summary: DC down, domain.sh with --cached-dc option doesn't start on slave node
(was: CLONE - DC down, domain.sh with --cached-dc option doesn't start on slave node)
DC down, domain.sh with --cached-dc option doesn't start on slave
node
----------------------------------------------------------------------
Key: AS7-1816
URL:
https://issues.jboss.org/browse/AS7-1816
Project: Application Server 7
Issue Type: Feature Request
Components: Scripts
Affects Versions: 7.0.1.Final
Reporter: Rostislav Svoboda
Assignee: Brian Stansberry
Priority: Critical
Fix For: 7.1.0.Alpha1
I have local copy of the domain configuration (using -backup), file
domain.cached-remote.xml exists.
Can't start domain.sh (with --cached-dc) when DC is down, script ends with could not
connect to remote server error.
*Details:*
(Master instance = MI, slave instance = SI, both on the same machine, EAP6 instances
copied into different directories)
MI> just start bin/domain.sh
SI: remove all domain/configuration/domain* (optional)
SI: change name attribute of host element in domain/configuration/host.xml
SI: change interfaces definition to public IP address in domain/configuration/host.xml
SI: change domain-controller definition to use remote domain controller (127.0.0.1 in my
case) in domain/configuration/host.xml
SI: run bin/domain.sh --backup
MI> shutdown EAP6 instance
SI: shutdown EAP6 instance
SI: make sure file domain/configuration/domain.cached-remote.xml
SI: run bin/domain.sh --cached-dc
SI: there is error, DC couldn't be contacted
log:
{code}
[Host Controller] 09:01:06,861 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO
Implementation Version 3.0.0.Beta3
[Host Controller] 09:01:11,980 WARN [org.jboss.as.domain.controller] (Controller Boot
Thread) Could not connect to remote domain controller 127.0.0.1:9999
[Host Controller] 09:01:12,083 ERROR [stderr] (Controller Boot Thread) Exception in
thread "Controller Boot Thread" java.lang.IllegalStateException:
java.net.ConnectException: Could not connect to remote server at 5000 within 5000ms
[Host Controller] 09:01:12,083 ERROR [stderr] (Controller Boot Thread) at
org.jboss.as.host.controller.RemoteDomainConnectionService.connect(RemoteDomainConnectionService.java:238)
[Host Controller] 09:01:12,084 ERROR [stderr] (Controller Boot Thread) at
org.jboss.as.host.controller.RemoteDomainConnectionService.register(RemoteDomainConnectionService.java:159)
[Host Controller] 09:01:12,084 ERROR [stderr] (Controller Boot Thread) at
org.jboss.as.host.controller.DomainModelControllerService.boot(DomainModelControllerService.java:291)
[Host Controller] 09:01:12,084 ERROR [stderr] (Controller Boot Thread) at
org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:83)
[Host Controller] 09:01:12,084 ERROR [stderr] (Controller Boot Thread) at
java.lang.Thread.run(Thread.java:662)
[Host Controller] 09:01:12,084 ERROR [stderr] (Controller Boot Thread) Caused by:
java.net.ConnectException: Could not connect to remote server at 5000 within 5000ms
[Host Controller] 09:01:12,084 ERROR [stderr] (Controller Boot Thread) at
org.jboss.as.protocol.ProtocolChannelClient.connect(ProtocolChannelClient.java:144)
[Host Controller] 09:01:12,085 ERROR [stderr] (Controller Boot Thread) at
org.jboss.as.host.controller.RemoteDomainConnectionService.connect(RemoteDomainConnectionService.java:221)
[Host Controller] 09:01:12,085 ERROR [stderr] (Controller Boot Thread) ... 4 more
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: