[
https://issues.jboss.org/browse/WFCORE-316?page=com.atlassian.jira.plugin...
]
Brian Stansberry commented on WFCORE-316:
-----------------------------------------
Another note: the reason persistence of changes to domain.cached-remote.xml can't
happen even if the slave connects to a DC is because in the --cached-dc case we use this
ConfigurationPersister:
https://github.com/wildfly/wildfly-core/blob/master/host-controller/src/m...
The store() method logs a warn and then returns a no-op PersistenceResource.
I think it probably can just not override the superclass, which is what
BackupRemoteDomainXmlPersister just above it does.
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: Enhancement
Components: Domain Management
Reporter: Manel Martinez Gonzalez
Assignee: Ken Wills
Fix For: 3.0.0.Beta1
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.4.11#64026)