activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Swen Moczarski (JIRA)" <>
Subject [jira] Commented: (AMQ-2736) KahaDB doesn't clean up old files
Date Mon, 25 Oct 2010 19:01:45 GMT


Swen Moczarski commented on AMQ-2736:

We also had some trouble with growing log files (version 5.4.1). I have two issues identified
with similar symptoms (but it seems to be another cause as to this issue):
* AMQ-2982: sticky log files on a rollback of a local transaction (test case and patch available)
* AMQ-2983: sticky log files on multiple concurrent consumers with local transacted sessions
(test case available)

If we only use non transacted sessions with auto-acknowledge, we have no problems.

> 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:, amq-2987-testcase.patch, amq-2987.patch, AMQ2736Test_should_with_this_diff.txt,
> 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