[
https://issues.apache.org/jira/browse/AMQ-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470277#comment-13470277
]
Vasile M commented on AMQ-2736:
-------------------------------
I just downloaded the version 5.6.0 of ActiveMQ.
I took the old configuration I was using for 5.5.1 and repeat the tests with my
application.
It seems the problems are fixed!
It means the fixed is not made in version 5.5.0 (like the bug is describing).
So please modify the describing(Fix Versions field) so the people should know
that the version 5.6.0 it contains the fix.
I won't open a new bug because it makes no sense.
> 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: AMQ2736Test_should_with_this_diff.txt, AMQ-2736.zip,
> amq-2987.patch, amq-2987-testcase.patch, 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
