[jira] Commented: (AMQ-2736) KahaDB doesn't clean up old files

[Abhishek C (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62828#action_62828
 ] 

Abhishek C commented on AMQ-2736:
-

@Swen Does using non transacted sessions with auto acknowledge clear the log 
files?
We have been facing a similar problem, however we are using Kaha Persistence 
Adapter on upgrading from 5.3.2 to 5.4.1. We had to upgrade to 5.4.1 because 
earlier using Durable Subs Topics our data files weren't getting cleaned up. 
Now our index-subs file are creating an issue. 

Any Final fix for this problem?

> 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, 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.

[jira] Created: (AMQ-2865) Perisistent Storage Files not getting cleaned up when using KahaPersistenceAdapter

[Abhishek C (JIRA)]

Perisistent Storage Files not getting cleaned up when using 
KahaPersistenceAdapter
--

 Key: AMQ-2865
 URL: https://issues.apache.org/activemq/browse/AMQ-2865
 Project: ActiveMQ
  Issue Type: Bug
  Components: Broker
 Environment: Windows XP / Java 1.6 / 4GB Ram
Reporter: Abhishek C


When using KahaPeristenceAdapter with Multiple Topics and Multiple Durable 
Subscriber, the persistent files created do not cleaned up. We are using 
Durable Topic Subscribers Clients which also act as producers. We are using 
selectors to filter messages as message broadcasted from one client is not 
supposed to be recieved by all. In this case when all consumers and producers 
are active files do not get cleaned up. Files for persistence storage keep on 
increasing. However, when selectors are removed the files get deleted at 
intervals.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.