[AMQ-2736] KahaDB doesn't clean up old files

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 5.3.2
• Fix Version/s: 5.5.0
• Assignee: Gary Tully
• Reporter: Adrian Trenaman
• Created: 18/May/10 09:38
• Updated: 02/Feb/15 13:07
• Resolved: 17/Feb/11 18:11

Description

Over time, we're seeing that kahadb doesn't clean up old journal files. As a result, we eventually run out of disk space, or rather, we hit our usage limits and our producers are slowed down by the producer flow control mechanism. Others have experienced this problem too (for example, see http://mail-archives.apache.org/mod_mbox/activemq-users/201002.mbox/[e-mail]%3E)

For now, we're moving back to the old amqPersistenceStore.

Issue Links

• breaks: AMQ-5542 KahaDB data files containing acknowledgements are deleted during cleanup

Sub-Tasks

• Sticky KahaDB log files due to concurrent consumer with local transaction: Resolved
• Sticky KahaDB log files due to local transaction rollback: Resolved