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

Bug 1260477

Summary: [GSS](6.4.z) HornetQ does not limit journal files when data replication being used
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Tyronne Wickramarathne <tywickra>
Component: HornetQAssignee: Yong Hao Gao <hgao>
Status: CLOSED DUPLICATE QA Contact: Miroslav Novak <mnovak>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.4.3CC: bbaranow, bmaxwell, csuconic, msvehla, rpelisse, rstancel, tywickra
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-06-13 11:41:48 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:
Attachments:
Description Flags
configurations none

Description Tyronne Wickramarathne 2015-09-07 03:56:13 UTC 
Description of problem:

HornetQ does not limit journal files when data replication being used. This behavior causes to create new bindings, journal,largemessages and paging folders during each server restart. 


Version-Release number of selected component (if applicable):

JBoss-EAP-6.4.3.GA (AS 7.5.3.Final-redhat-2) 
HornetQ-2.3.25.SP3 (2.3.x, 123)

How reproducible:
Always

Steps to Reproduce:
1. Please install two JBoss-EAP-6.4.3 server instances, NodeA and NodeB
2. Please configure a new server profile based on full-ha; name the new server profile as full-ha-two
3. Please configure "main-server-group" with "full-ha" profile and "other-server-group" with "full-ha-two" server profile.
4. Disable other server profiles. 
5. The server-two needs to belong to main-server-group, server-three should belong to the "other-server-group"
6. On NodeA please configure the following :
   "full-ha" profile as a live server with having the backup-group-name "foo"
   "full-ha-two" profile as a backup server with having the backup-group-name "bar"

7. On NodeA please configure the following :
   "full-ha" profile as a live server with having the backup-group-name "bar"
   "full-ha-two" profile as a backup server with having the backup-group-name "foo"

8. Please start the NodeA
9. Please start the NodeB and observer the "data" folder
10. Please restart the NodeB a couple times. You would notice the said folder sets keep growing during each server restart.

Actual results:
The replication mechanism keeps creating a set of folders during each server restart.

Expected results:
The replication mechanism needs just a set of folders for each server instance.


Additional info:
Comment 1 Tyronne Wickramarathne 2015-09-07 04:02:42 UTC 
Created attachment 1070822 [details]
configurations
Comment 7 Radovan STANCEL 2017-06-13 11:41:48 UTC 

*** This bug has been marked as a duplicate of bug 1348322 ***