[jboss-jira] [JBoss JIRA] (WFCORE-316) Slave host does not register to DC when starting with --cached-dc and DC is available

[Brian Stansberry (JIRA)]

     [ https://issues.jboss.org/browse/WFCORE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry moved WFLY-818 to WFCORE-316:
----------------------------------------------

        Project: WildFly Core  (was: WildFly)
            Key: WFCORE-316  (was: WFLY-818)
    Component/s: Domain Management
                     (was: Domain Management)


> 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
>
> NOTE: this is related to AS7-4281 (see https://issues.jboss.org/browse/AS7-4281?focusedCommentId=12682058&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12682058 )
> 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.8#6338)