[
https://issues.jboss.org/browse/AS7-4412?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-4412:
---------------------------------------
The likely fix for this, at least for the short term, will be to change the help text to
more clearly state the current behavior. I want the help text to reflect the actual
behavior for 7.1.2 but am not sure we can adequately test changing the actual behavior in
that time frame.
Slave host does not register to DC when starting with --cached-dc and
DC is available
-------------------------------------------------------------------------------------
Key: AS7-4412
URL:
https://issues.jboss.org/browse/AS7-4412
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.1.1.Final
Reporter: Manel Martinez
Assignee: Brian Stansberry
Priority: Critical
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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira