[
https://issues.apache.org/activemq/browse/AMQ-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62522#action_62522
]
Gary Tully commented on AMQ-2736:
---------------------------------
The scenario that needs to be tested, for future
reference:{code}ackMessageFileMap = {2=[1], 3=[1, 2], 4=[2, 3, 4], 5=[4, 5],
6=[5, 6], 7=[6, 7], 8=[7, 8]}
gCandidateSet = [2, 3, 4, 5, 6, 7]{code}
> 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
> Priority: Critical
> Attachments: AMQ-2736.zip, amq-2987-testcase.patch, amq-2987.patch,
> AMQ2736Test_should_with_this_diff.txt
>
>
> 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.
