[
https://issues.apache.org/jira/browse/AMQ-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469411#comment-13469411
]
Vasile M commented on AMQ-2736:
-------------------------------
Hi guys,
I am using the version 5.5.1 of ActiveMQ and I can still reproduce this problem.
I saw you have fixed some problems but I think my case is different.
The most connected bug with my issue is
:https://issues.apache.org/jira/browse/AMQ-2983
In my case I am no using local transactions, I am using global transaction
(XATransactions) and then I always comit the transactions and still the log
files are not deleted.
The JMS Connections Pool in my case it is defined in glassfish using the
ActiveMQ Resource Adapter.
Have you tested with global transactions 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
