Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-316

Slave host does not register to DC when starting with --cached-dc and DC is available

    XMLWordPrintable

Details

    Description

      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

      Attachments

        Issue Links

          Activity

            People

              kwills@redhat.com Ken Wills
              mmartinez-gonzalez Manel Martinez Gonzalez (Inactive)
              Votes:
              14 Vote for this issue
              Watchers:
              16 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: