[MQ-72] newTxnLog enabled broker generates a really large MQ 'txnlog' file for long running transacted client Created: 03/Jan/11  Updated: 17/Mar/11  Resolved: 04/Jan/11

Status: Closed
Project: mq
Component/s: broker-core
Affects Version/s: 4.4u1, 4.4u2, 4.5
Fix Version/s: 4.5

Type: Bug Priority: Major
Reporter: amyk Assignee: amyk
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Dependency
blocks GLASSFISH-15423 [STRESS] [BigApps] [Umbrella-Issue] 2... Closed
Tags: newTxnLog

 Description   

This is reported by GlassFish QE on GlassFish 3.1 stress test (RichAccess):
"The run is generating a really large MQ transaction log - of the order of a few tens of GB over a period of a few days. Below is a list of the largest files on one of the instances where the size hit ~45 GB (in 10 days).
45379411901 ./glassfish3/glassfish/nodes/agent4/instance103/imq/instances/stclusterinstance103/fs370/txnlog
......



 Comments   
Comment by amyk [ 04/Jan/11 ]

cpSize in txnlog writer became negative when max size < cpOffset, bug 7010372 is filed and fixed in 4.5build24

Comment by varunrupela [ 11/Jan/11 ]

This issue has been verified as fixed with GF nightly build 37 from 10th Jan.

Comment by amyk [ 12/Jan/11 ]

close the issue as the fix has been verified

Generated at Sat Jan 21 14:19:58 UTC 2017 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.