[
https://issues.apache.org/activemq/browse/AMQ-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christer WIkman reopened AMQ-2736:
----------------------------------
We running:
http://people.apache.org/~jgenender/apache-activemq-5.4.1-AMQ2736-bin.tar.gz
and we are still experience problems with log files that are not deleted.
I deployed the fix yesterday with a new kahadb and this morning I had 155 log
files with only 43 messages on two DLQ queues. I deleted the DLQ queues and
only 12 log files where deleted. Currently,. I have 144 log files and nothing
in the queues.
> 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/%3c27502591.p...@talk.nabble.com%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.
