[
https://issues.jboss.org/browse/WFCORE-316?page=com.atlassian.jira.plugin...
]
Brian Stansberry reassigned WFCORE-316:
---------------------------------------
Assignee: luck3y
Ken, I'm assigning this as one of several in the general area of how various Host
Controllers interact. We should look at them in total and come up with a strategy, not do
them piecemeal.
Slave host does not register to DC when starting with --cached-dc and
DC is available
-------------------------------------------------------------------------------------
Key: WFCORE-316
URL:
https://issues.jboss.org/browse/WFCORE-316
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Reporter: Manel Martinez Gonzalez
Assignee: luck3y
NOTE: this is related to AS7-4281 (see
https://issues.jboss.org/browse/AS7-4281?focusedCommentId=12682058&pa...
)
When a slave host is started with --cached-dc option it won't register to Domain
Controller although it's available. domain.sh help says "If this host is not the
Domain Controller and cannot contact the Domain Controller at boot, boot using a locally
cached copy of the domain configuration (see --backup)" and this is not really
happening because slave host never contact to DC with --cached-dc
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)