Return-Path: Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: (qmail 2653 invoked from network); 7 Oct 2010 13:51:06 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 7 Oct 2010 13:51:06 -0000 Received: (qmail 23864 invoked by uid 500); 7 Oct 2010 13:51:06 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 23836 invoked by uid 500); 7 Oct 2010 13:51:06 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 23828 invoked by uid 99); 7 Oct 2010 13:51:06 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Oct 2010 13:51:06 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Oct 2010 13:51:04 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o97Dogx5029205 for ; Thu, 7 Oct 2010 13:50:42 GMT Message-ID: <5187742.49221286459442674.JavaMail.jira@thor> Date: Thu, 7 Oct 2010 09:50:42 -0400 (EDT) From: "Jeff Genender (JIRA)" To: dev@activemq.apache.org Subject: [jira] Commented: (AMQ-2736) KahaDB doesn't clean up old files In-Reply-To: <4769034.461274175614021.JavaMail.jira@thor> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: ae95407df07c98740808b2ef9da0087c X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/activemq/browse/AMQ-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62431#action_62431 ] 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: 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.