Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1348322

Summary: [GSS](6.4.z) HornetQ Server should always remove old files beyond getMaxSavedReplicatedJournalsSize
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Clebert Suconic <csuconic>
Component: HornetQAssignee: Peter Palaga <ppalaga>
Status: CLOSED CURRENTRELEASE QA Contact: Erich Duda <eduda>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.4.8CC: bmaxwell, cdewolf, csuconic, dosoudil, eduda, fgavrilo, jtruhlar, mnovak, msvehla, pmackay, ppalaga, tom.ross, tywickra
Target Milestone: CR2   
Target Release: EAP 6.4.10   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-17 13:00:02 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1339868, 1344476, 1348237    

Description Clebert Suconic 2016-06-20 19:57:55 UTC 
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.
Comment 1 Peter Palaga 2016-06-23 10:37:08 UTC 
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.
Comment 2 Peter Palaga 2016-06-24 07:30:05 UTC 
Assigning to me which means in this case that I'll coordinate rather than actually fix.
Comment 15 Petr Penicka 2017-01-17 13:00:02 UTC 
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.
Comment 16 Radovan STANCEL 2017-06-13 11:41:48 UTC 
*** Bug 1260477 has been marked as a duplicate of this bug. ***