Return-Path: Delivered-To: apmail-geronimo-activemq-users-archive@www.apache.org Received: (qmail 97592 invoked from network); 18 Jul 2006 04:01:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 18 Jul 2006 04:01:00 -0000 Received: (qmail 6481 invoked by uid 500); 18 Jul 2006 04:01:00 -0000 Delivered-To: apmail-geronimo-activemq-users-archive@geronimo.apache.org Received: (qmail 6465 invoked by uid 500); 18 Jul 2006 04:01:00 -0000 Mailing-List: contact activemq-users-help@geronimo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: activemq-users@geronimo.apache.org Delivered-To: mailing list activemq-users@geronimo.apache.org Received: (qmail 6456 invoked by uid 99); 18 Jul 2006 04:00:59 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Jul 2006 21:00:59 -0700 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of james.strachan@gmail.com designates 66.249.92.169 as permitted sender) Received: from [66.249.92.169] (HELO ug-out-1314.google.com) (66.249.92.169) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Jul 2006 21:00:59 -0700 Received: by ug-out-1314.google.com with SMTP id o2so1092101uge for ; Mon, 17 Jul 2006 21:00:37 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=minaXaZuAsQui/DiobkIMiyt7U5IDtuNSo7QCuRqGoCNAdmVQM9bYUIq68CuVP5Eavfc8Eq6bNGNSEAQIIn0Wqrs1ZlksFrpIpfCVTDgZRNK2SfAD3NJbpKl2OQ6s7iAIthrqEAGo1wjM0rVvEEszjaulexFtKe4emXVeuSPi6M= Received: by 10.78.177.3 with SMTP id z3mr1249208hue; Mon, 17 Jul 2006 21:00:37 -0700 (PDT) Received: by 10.78.174.8 with HTTP; Mon, 17 Jul 2006 21:00:37 -0700 (PDT) Message-ID: Date: Tue, 18 Jul 2006 05:00:37 +0100 From: "James Strachan" To: activemq-users@geronimo.apache.org Subject: Re: activemq database cleanup In-Reply-To: <4e6f67720607170727s7516acecl6706de7fe89e6328@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4e6f67720607170727s7516acecl6706de7fe89e6328@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On 7/17/06, Jamie McCrindle wrote: > hi all, > > does activemq delete consumed / expired messages from the database on > its own or should i have a job deleting old messages running in the > background? It generally does it on its own. For queues messages are deleted immediately (though with the use of the journal that only happens when a checkpoint occurs). For durable topics there is a background thread which goes and tries to delete any message which has been consumed by all the durable subscribers. For expired messages we are currently quite passive and kinda zap them as we go along. I'm sure we could be a bit more aggressive in our removal of expired messages. > corollary: if activemq is doing the cleanup and the database is > filling up should i be worried about my app leaking messages that > aren't being consumed? The main thing is to look at say queues in JMX and check that no queues are filling up etc. The database size can fill up due to the asynchronous nature of both the journal and the asynchronous deletion of used resources (like durable topics or expired messages on queues). So there's normally a bit of a lag. -- James ------- http://radio.weblogs.com/0112098/