Description of problem: There is a mixup on the semantics for getMaxSavedReplicatedJournalsSize. When a dedicated backup is starting it will simply ignore the maxSavedReplicatedJournalSize and make a new copy. When a failback happens the parameter is used and won't let the server start at all, leaving the user without a backup. The server should remove old files beyond getMaxSavedReplicatedJournalsSize(). The semantic would be equalized through this change. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Restart a failback server in replication many times Actual results: The server won't be started Expected results: Old folders to be removed and a number of configurable backups to be left on the folder.
Clebert, is it OK if I start working on this? I am asking because this is 100% your domain and I may need much longer to get things right than you or somebody else from the messaging team.
Assigning to me which means in this case that I'll coordinate rather than actually fix.
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.
*** Bug 1260477 has been marked as a duplicate of this bug. ***