JBoss Domain Slave hosts cannot reconnect after domain controller has been restarted / reloaded

Environment

• Red Hat JBoss Enterprise Application Platform (EAP)

  • 6.4.20

• rollout-plan on domain.xml configuration.

    rollout-plan add --name=my-plan --content={rollout groupa^groupb}
  

Issue

• The Slave Host Controllers in a JBoss Domain aren't able to create a connexion after a restart of the Domain Controller.
  According to the logs, the "apply-remote-domain-model" CLI command of the controllers fails.

• Getting error JBAS014687: Resource is immutable.

Resolution

Update to the newest CP (not yet available) or upgrade to EAP7.

Root Cause

Known bug This content is not included.Host controllers can not connect to domain after creating a rollout plan and restarting the master host controller.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.