Return-Path: X-Original-To: apmail-activemq-dev-archive@www.apache.org Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E8B4243C5 for ; Mon, 23 May 2011 13:44:24 +0000 (UTC) Received: (qmail 5663 invoked by uid 500); 23 May 2011 13:44:24 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 5628 invoked by uid 500); 23 May 2011 13:44:24 -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 5620 invoked by uid 99); 23 May 2011 13:44:23 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 May 2011 13:44:23 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of chirino@gmail.com designates 209.85.212.43 as permitted sender) Received: from [209.85.212.43] (HELO mail-vw0-f43.google.com) (209.85.212.43) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 May 2011 13:44:19 +0000 Received: by vws10 with SMTP id 10so5511312vws.2 for ; Mon, 23 May 2011 06:43:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=NdbjTHIyD9N3yR0qNA8b7axEApb8ZOVbv9Nf6PuAV0U=; b=hjYKChUSJ/1KqBzspGecuxZL4KKkgYL/HLlokQGniZsIwYq8pnlj8YSOWgi/YZfQll VcU7PnTDfZAcSPsTESQMMau1kXD8Qryvrl0Wi/4gQlW8TMWjpb6fLCBmcPjXhxyr+z7w J+MpDUTg8IQE0jIEsFnZDIfzpwQXKqHl8lpLk= 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:cc:content-type; b=luGrUdzUy94Jk8E/sjsLVyZRG3fqaLjCufr2HPmrUfzoWver/84uZw2mbFQ6dvYOBd eDUfIEUvUht+Z/GKeU1c6mCN92j42G6iJFnmcTwGPA7tWBjPMxrLG0xcigSgQrrJbGEp aKRq3ugGyptznkxAyS/gRs1fD55uDPyb+tQu8= MIME-Version: 1.0 Received: by 10.52.115.232 with SMTP id jr8mr3365098vdb.38.1306158238404; Mon, 23 May 2011 06:43:58 -0700 (PDT) Sender: chirino@gmail.com Received: by 10.52.157.233 with HTTP; Mon, 23 May 2011 06:43:58 -0700 (PDT) In-Reply-To: <20110520074447.18af.abe10f7e5afbbb3a79ce619739541149@cern.ch> References: <20110520074447.18af.abe10f7e5afbbb3a79ce619739541149@cern.ch> Date: Mon, 23 May 2011 09:43:58 -0400 X-Google-Sender-Auth: INWFcqM2Jrv8MVlA46GjSNLvIeA Message-ID: Subject: Re: DLQ in Apollo From: Hiram Chirino To: Lionel Cons Cc: dev@activemq.apache.org Content-Type: text/plain; charset=ISO-8859-1 I've opened up APLO-16 to track the feature request. I would be nice to eventually get the feature in too! Regards, Hiram FuseSource Web: http://fusesource.com/ Connect at CamelOne May 24-26 The Open Source Integration Conference On Fri, May 20, 2011 at 1:49 AM, Lionel Cons wrote: > Hiram, > > We currently use Dead Letter Queues in ActiveMQ to analyze which > messages expired. > > Do you have plans to support DLQs in Apollo? > > Wo don't need fancy policies, we just need to tell the broker that > expired messages should be put into a named queue that we will purge. > For us, a single DLQ per broker is enough. > > Cheers, > > Lionel >