Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 20080 invoked from network); 3 Apr 2009 08:40:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 3 Apr 2009 08:40:17 -0000 Received: (qmail 52464 invoked by uid 500); 3 Apr 2009 08:40:16 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 52403 invoked by uid 500); 3 Apr 2009 08:40:16 -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 52393 invoked by uid 99); 3 Apr 2009 08:40:16 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Apr 2009 08:40:16 +0000 X-ASF-Spam-Status: No, hits=2.4 required=10.0 tests=HTML_MESSAGE,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of chubrilo@gmail.com designates 209.85.219.164 as permitted sender) Received: from [209.85.219.164] (HELO mail-ew0-f164.google.com) (209.85.219.164) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Apr 2009 08:40:06 +0000 Received: by ewy8 with SMTP id 8so1006755ewy.38 for ; Fri, 03 Apr 2009 01:39:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=Y2h1o9IrRshfQpyTSjI2+EEhSEFg70kl7iNSoVi43g4=; b=AcffGyipUs1rQ+sDfKHDj/J4AUvjXgluijsSc3vH9KOAg1LSQcMs/8UohK0xoE3sSJ uis1p606FOlvSxra/QDmt/RI4G/CkuxEsbzdIGxfGpO9+xvkGor5bzF8a85jucsr5tuq gEg61gvxOoKCNb0DVDtCkUENvvad6uDOytbMg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=AW2p/Uv22cCwrBSVFZuw0ve2t6w4JyahHIUS/3OQQEDWb+aXOxEWuVOGar4O0te+xv Xt5NaWdN/pxwPhB/AbpqsmqaC1sCSznv9Dl4jmeQpK2K6zn5qdBkkVmkaOsn+X6WRnSL 8PTWySSX8PefNoUechV7zy2RrOiWNX8/7mqyU= MIME-Version: 1.0 Sender: chubrilo@gmail.com Received: by 10.210.45.17 with SMTP id s17mr717038ebs.93.1238747985841; Fri, 03 Apr 2009 01:39:45 -0700 (PDT) In-Reply-To: <22851111.post@talk.nabble.com> References: <22851111.post@talk.nabble.com> Date: Fri, 3 Apr 2009 10:39:45 +0200 X-Google-Sender-Auth: c13d23593dc52040 Message-ID: <36e91d9d0904030139w22f07602i3e611438e608765f@mail.gmail.com> Subject: Re: Messages not being expired onto DLQ From: Dejan Bosanac To: users@activemq.apache.org Content-Type: multipart/alternative; boundary=0015174bdf10a990380466a27d2a X-Virus-Checked: Checked by ClamAV on apache.org --0015174bdf10a990380466a27d2a Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi, you can try the latest snapshot http://activemq.apache.org/download.html to see if the issue has been fixed. Or you can try the latest fuse release http://fusesource.com/products/enterprise-activemq/. Cheers -- Dejan Bosanac Open Source Integration - http://fusesource.com/ ActiveMQ in Action - http://www.manning.com/snyder/ Blog - http://www.nighttale.net On Thu, Apr 2, 2009 at 6:33 PM, bendg wrote: > > Hi > > There appears to be an issue with expired messages on ActiveMQ version > 5.2.0. Expired messages are not immediately moved to the DLQ when they > expire. Instead they remain in the queue until they have exceeded their > expiry date by several minutes AND another message is delivered to the > queue. When these two conditions are met the expired messages are moved to > the DLQ. However, I have been unable to predict with any accuracy exactly > when messages will be moved. > > It seems that this issue is covered by > https://issues.apache.org/activemq/browse/AMQ-1112, which indicates that > the > issue is resolved in version 5.3.0. > > Is it possible to obtain a build of version of 5.3.0? When is it due for > release? > > I have attempted to use version 4.1 (with the patched web-console) but this > version does not appear to expire messages into the DLQ at all. > > Of course, if you have any suggestions as to how I can overcome this > limitation then I would be very grateful. > > Unfortunately, this functionality is key to the system I am using and if I > can't overcome it (without resorting to writing a standalone housekeeping > application) I will have to use another broker. This is disappointing as I > have been otherwise very impressed with ActiveMQ. > > Thanks > -- > View this message in context: > http://www.nabble.com/Messages-not-being-expired-onto-DLQ-tp22851111p22851111.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > --0015174bdf10a990380466a27d2a--