[
https://issues.apache.org/jira/browse/AMQ-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13049295#comment-13049295
]
Stephanie Miotke commented on AMQ-2736:
---------------------------------------
This does not appear to be fixed in 5.5.
I have a queue that holds onto a message every once in a while due to bad
formatting or what-have-you (not something I can immediately correct). Since
KahaDB requires the need to retain the full contents of the DB file while one
message persists, it will cause the file system to grow dramatically if you
alter the default kahaDB file size at all. With a DB file of 96 megs each I've
eaten up almost 5 gigs of disk space in 34 pending messages all less than 2000
bytes each. I'm going to begin auto purging the offending queue (since we don't
require those messages), however it would be preferred to have some automatic
process possibly automatically consolidate the DB once its reached a
pre-configured limit?
> KahaDB doesn't clean up old files
> ---------------------------------
>
> Key: AMQ-2736
> URL: https://issues.apache.org/jira/browse/AMQ-2736
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.3.2
> Reporter: Adrian Trenaman
> Assignee: Gary Tully
> Priority: Critical
> Fix For: 5.5.0
>
> Attachments: AMQ-2736.zip, AMQ2736Test_should_with_this_diff.txt,
> MyKahaDBStore.java, amq-2987-testcase.patch, amq-2987.patch
>
>
> 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/%[email protected]%3E)
> For now, we're moving back to the old amqPersistenceStore.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
