activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Genender (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQ-2736) KahaDB doesn't clean up old files
Date Thu, 07 Oct 2010 13:43:42 GMT

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

Jeff Genender commented on AMQ-2736:
------------------------------------

Looks like there *maybe* a wait/lock condition on multiple "KahaDB Scheduler" threads...

I took the attached example and was able to reproduce the problem.  A thread dump showed waits
on the "KahaDB Scheduler".  I knocked out one of the schedulers and it appears to clean up.

Hence... can you please try setting schedulerSupport="false" on the broker configuration and
see if the files no longer grow?   This may be a work around for the time being.  Hopefully
this is in the right direction...

> 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
>
>
> 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.post@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.


Mime
View raw message