[
https://issues.apache.org/jira/browse/AMQ-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469447#comment-13469447
]
Vasile M commented on AMQ-2736:
-------------------------------
I want to add to my provious comment that we are using the CPP library CMS for
ActiveMQ with stomp.
We have one producer and one subscriber and this already causing problems.
The logs are growing.
In C++ we use Session::AUTO_ACKNOWLEDGE and even in this case the log files are
not deleted.
We write(using a producer) in the queue and and another process is
reading(using a listener) we never have many messages in the queue.
QueueName Number of pending messages Number of listener Messages
Enqueued Messages Dequeued
queuename 0 1 21522
21522
This is maybe a new use-case too ?
> 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
