Fix for 3736 : Replication dynamic purge delay change not properly taken in...

gbellato

22.27.2009 8ac679b8e8f53b0cf59d644a1948cd227bf594af

Fix for 3736 : Replication dynamic purge delay change not properly taken into account.

When the replication log purge delay is set before any changes is done on the topology,
the purge delay was calculated wrong and the purge was therefore not happening as expected.

 opendj-sdk/opends/src/server/org/opends/server/replication/server/ReplicationServer.java

@@ -22,7 +22,7 @@
 * CDDL HEADER END
 *
 *
 *      Copyright 2006-2008 Sun Microsystems, Inc.
 *      Copyright 2006-2009 Sun Microsystems, Inc.
 */
package org.opends.server.replication.server;
import static org.opends.messages.ReplicationMessages.*;
@@ -645,14 +645,14 @@
      replicationServers = new ArrayList<String>();

    queueSize = configuration.getQueueSize();
    long newPurgeDelay = configuration.getReplicationPurgeDelay()*1000;
    long newPurgeDelay = configuration.getReplicationPurgeDelay();
    if (newPurgeDelay != purgeDelay)
    {
      purgeDelay = newPurgeDelay;
      // propagate
      for (ReplicationServerDomain domain : baseDNs.values())
      {
        domain.setPurgeDelay(purgeDelay);
        domain.setPurgeDelay(purgeDelay*1000);
      }
    }