You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Pierre-Arnaud Marcelot (JIRA)" <ji...@apache.org> on 2013/01/04 16:12:12 UTC

[jira] [Created] (DIRSERVER-1789) Changes to an existing replication consumer may not be taken into account

Pierre-Arnaud Marcelot created DIRSERVER-1789:
-------------------------------------------------

             Summary: Changes to an existing replication consumer may not be taken into account
                 Key: DIRSERVER-1789
                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1789
             Project: Directory ApacheDS
          Issue Type: Bug
    Affects Versions: 2.0.0-M9
            Reporter: Pierre-Arnaud Marcelot
            Priority: Critical
             Fix For: 2.0.0-M10


While testing the replication configuration in the ApacheDS v2 Configuration plugin, I noticed that changes to an existing replication consumer may not be taken into account.

If I create a replication consumer, save it and restart the server, the replication is correctly set up and an entry is created under the "ou=consumers,ou=system" node.
This entry saves a few values from the replication configuration like the search base, the alias dereferencing mode, etc.

If update the configuration of the replication consumer and restart the server again. The values of the entries are not updated and no longer in sync with the updated configuration.

In that case, I think the replication may fail.

I would be great to have support for editing the configuration of the replication consumers.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira