Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 5136 invoked from network); 17 Apr 2008 16:41:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 17 Apr 2008 16:41:02 -0000 Received: (qmail 13383 invoked by uid 500); 17 Apr 2008 16:41:01 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 13360 invoked by uid 500); 17 Apr 2008 16:41:01 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 13351 invoked by uid 99); 17 Apr 2008 16:41:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Apr 2008 09:41:01 -0700 X-ASF-Spam-Status: No, hits=3.7 required=10.0 tests=DNS_FROM_OPENWHOIS,FORGED_HOTMAIL_RCVD2,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Apr 2008 16:40:09 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1JmX9x-0007rq-MX for users@activemq.apache.org; Thu, 17 Apr 2008 09:40:29 -0700 Message-ID: <16746607.post@talk.nabble.com> Date: Thu, 17 Apr 2008 09:40:29 -0700 (PDT) From: tanshul22 To: users@activemq.apache.org Subject: Re: [activemq-user] Persistent messages in the database In-Reply-To: <200511052223.jA5MNr6Q019796@whale.cs.indiana.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: tanshul22@hotmail.com References: <200511052223.jA5MNr6Q019796@whale.cs.indiana.edu> X-Virus-Checked: Checked by ClamAV on apache.org I had the same problem. I had a filter to acknowledge the receipt of a message installed as a broker plugin. Just needed to call super.acknowledge() in my filter where i was overwriting the acknowledge and now all messages get consumed of the DB. Yi Huang wrote: > > Hi, > > > > I am using auto-acknowledge on both the subscriber and publisher sides > without transaction. The publisher uses the default Persistent delivery > mode. I use mySQL for persistency on activeMQ and do not use journal so > that > I can see all the messages. I noticed that all the published messages are > stored in the database as required by the persistent delivery mode. > > > > However, I wonder whether there is some mechanism to remove the delivered > messages from the database. I noticed that even if the message is > delivered > to all the consumers successfully, it still stays in the database. If I > set > TimeToLive on the publisher, the message topic will be changed to > something > like "org.activemq.deadletter.topic1", but the entry still stays in the > database. This will exhaust the database space. > > > > Is this the correct behavior? Why is it necessary to keep all the messages > in database after their delivery? > > > > Thanks, > > > > Yi > > > -- View this message in context: http://www.nabble.com/-activemq-user--Persistent-messages-in-the-database-tp1352168s2354p16746607.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.