activemq-dev mailing list archives

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


Jeff Genender commented on AMQ-2736:

I ran the attached example and was able to reproduce it and indeed appears to endlessly grow.
 I did a thread dump during the condition and there appears to be a possible locking problem
with multiple "KahaDB Scheduler" threads.

As an experiment I killed one of the KahaDB Schedulers and it seemed to clean up.  I ran the
example several times and it seems to clean up.  So this *may* be the culprit.

So please try this as a work around...

In the broker configuration set schedulerSupport="false" and see if the files clean up.  This
may help until we identify the waits on multiple schedulers.

> KahaDB doesn't clean up old files
> ---------------------------------
>                 Key: AMQ-2736
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.3.2
>            Reporter: Adrian Trenaman
>            Priority: Critical
>         Attachments:
> 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
> 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.

View raw message