[
https://issues.apache.org/activemq/browse/AMQ-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63192#action_63192
]
Christer WIkman commented on AMQ-2736:
--------------------------------------
I deployed yesterday in stage latest 5.5-SNAPSHOT and it seems that the problem
is solved. This morning I had 17 log files, but after I deleted DLQ queues with
messages I ended up with only 1 log file! When I used 5.4.1 the files grow with
approx 50-100 files per day.
We are not comfortable deploying 5.5-SNAPSHOT in production. Can anyone provide
me with a patch for 5.4.1? Currently, I cannot recommend using version 5.4.1 in
production without the combined fixes from 5.5-SNAPSHOT.
> KahaDB doesn't clean up old files
> ---------------------------------
>
> Key: AMQ-2736
> URL: https://issues.apache.org/activemq/browse/AMQ-2736
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.3.2
> Reporter: Adrian Trenaman
> Assignee: Dejan Bosanac
> Priority: Critical
> Fix For: 5.5.0
>
> Attachments: AMQ-2736.zip, amq-2987-testcase.patch, amq-2987.patch,
> AMQ2736Test_should_with_this_diff.txt, MyKahaDBStore.java
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
