Return-Path: X-Original-To: apmail-directory-dev-archive@www.apache.org Delivered-To: apmail-directory-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0A543E5C5 for ; Fri, 4 Jan 2013 15:12:20 +0000 (UTC) Received: (qmail 5466 invoked by uid 500); 4 Jan 2013 15:12:19 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 5119 invoked by uid 500); 4 Jan 2013 15:12:14 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 4058 invoked by uid 99); 4 Jan 2013 15:12:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Jan 2013 15:12:12 +0000 Date: Fri, 4 Jan 2013 15:12:12 +0000 (UTC) From: "Pierre-Arnaud Marcelot (JIRA)" To: dev@directory.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (DIRSERVER-1789) Changes to an existing replication consumer may not be taken into account MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 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