Fix for 4298 : changelog db files not purged cause disk full error

gbellato

26.00.2009 d2e8ea2ee8f1c855b7434bbc922579e0ecb1229e

Fix for 4298 : changelog db files not purged cause disk full error

Set the follwoing DB parameters :
 - enable DB logging as for the jeb DB to allow debugging in case the problem happens again
 - use priority checkpointing
 - use 2 cleaner threads instead of 1
 

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

@@ -89,6 +89,9 @@
    envConfig.setAllowCreate(true);
    envConfig.setTransactional(true);
    envConfig.setConfigParam("je.cleaner.expunge", "true");
    envConfig.setConfigParam("java.util.logging.FileHandler.on", "true");
    envConfig.setConfigParam("je.cleaner.threads", "2");
    envConfig.setConfigParam("je.checkpointer.highPriority", "true");

    // Tests have shown that since the parsing of the Replication log is always
    // done sequentially, it is not necessary to use a large DB cache.