Return-Path: X-Original-To: apmail-activemq-users-archive@www.apache.org Delivered-To: apmail-activemq-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 15D7B10191 for ; Fri, 8 Nov 2013 17:21:27 +0000 (UTC) Received: (qmail 2541 invoked by uid 500); 8 Nov 2013 17:21:26 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 2264 invoked by uid 500); 8 Nov 2013 17:21:22 -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 1971 invoked by uid 99); 8 Nov 2013 17:21:20 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Nov 2013 17:21:20 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of christian.posta@gmail.com designates 209.85.215.51 as permitted sender) Received: from [209.85.215.51] (HELO mail-la0-f51.google.com) (209.85.215.51) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Nov 2013 17:21:16 +0000 Received: by mail-la0-f51.google.com with SMTP id ep20so1951756lab.24 for ; Fri, 08 Nov 2013 09:20:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=9R7Sj8NpSKqvtWE3Qe13kyyrqdt7VAmukN1s/S1zJH0=; b=GHnCkVCjrjAcTXeod3KgrqgaCOCDFIIMZsrBtdZWlUGg2C+vfObJAlwkIHTxUGM7EG UKrpmleMWNJ17nKwQle92mqlyAWDAUh0xKuWj1AdfOQVC9AnmrKh8Ns1oVBBH2LkFHQA tgj37xQ3D966gRnTV1ORof/ToIP6pXe1s16TkoEjEeTyNSyUFjfYYvnt/ov1S7rY9TNp wAF4SWpJNw6casqC8uPcxO0yl7bmbn49tNxpmuUzCSoeZkJAy+XOtgyS8S4kydzUoK1L ddrFrD4AXagoLTIF1zLqMExl3GtslrGjAQVs1ov4oTrw3iVUUDNogVhzNm3c+MkTpA88 lJwg== MIME-Version: 1.0 X-Received: by 10.152.21.133 with SMTP id v5mr11704367lae.14.1383931254851; Fri, 08 Nov 2013 09:20:54 -0800 (PST) Received: by 10.114.243.139 with HTTP; Fri, 8 Nov 2013 09:20:54 -0800 (PST) In-Reply-To: <443BCE38E921434394B45FF0813FA578053DA484@MSGEXSV21106.ent.wfb.bank.corp> References: <443BCE38E921434394B45FF0813FA578053D96F0@MSGEXSV21106.ent.wfb.bank.corp> <443BCE38E921434394B45FF0813FA578053DA10C@MSGEXSV21106.ent.wfb.bank.corp> <443BCE38E921434394B45FF0813FA578053DA484@MSGEXSV21106.ent.wfb.bank.corp> Date: Fri, 8 Nov 2013 10:20:54 -0700 Message-ID: Subject: Re: ActiveMQ.DLQ From: Christian Posta To: "users@activemq.apache.org" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Well, it would be the same as a user-queue... ie.. if something tries to send to the DLQ, it will be auto-created. So for example, when the broker checks for expiring messages upon dispatch, if it finds any it will send them to the DLQ... if that queue, "ActiveMQ.DLQ" is not already in the system (it's not on a fresh broker install, for example), then it will be auto-created just like a user queue is. On Fri, Nov 8, 2013 at 9:26 AM, wrote: > After reading the wiki, I see the following: > > This means that a client can create a new Queue or Topic dynamically eith= er by > calling createQueue() or createTopic() on a JMS Session > creating an instance of ActiveMQTopic or ActiveMQQueue and possibly regis= tering them in JNDI > > This still isn't telling me how ActiveMQ knows when to create the ActiveM= Q.DLQ. Are you saying that the client would have to dynamically create it,= or again, is it something at the server side system config that's telling = it to create a DLQ if messages cant be delivered, expired, etc? > > Regards, > > Barry Barnett > WMQ Enterprise Services & Solutions > > > -----Original Message----- > From: Christian Posta [mailto:christian.posta@gmail.com] > Sent: Friday, November 08, 2013 9:57 AM > To: users@activemq.apache.org > Subject: Re: ActiveMQ.DLQ > > Nope :) > > http://activemq.apache.org/how-do-i-create-new-destinations.html > > But it's completely configurable.. ie, you can specify whether destinatio= ns should be auto-created.. or you can use security to lockdown people from= creating destinations on demand... lots of ways to do it, but by default t= he destinations are auto-created as described in the wiki above. > > If you want to have destinations created when the broker starts up, you c= ould do something like this in the activemq.xml file: > > > > > > > > > > > > > > > but it's not necessary.... > > On Fri, Nov 8, 2013 at 5:58 AM, wrote: >> Thank you. But doesn't it have to be in some configuration file somewhe= re so that the broker knows how to create it when it's needed? I don't see= it in the activemq.xml file. >> >> Regards, >> >> Barry Barnett >> WMQ Enterprise Services & Solutions >> >> >> >> -----Original Message----- >> From: Christian Posta [mailto:christian.posta@gmail.com] >> Sent: Thursday, November 07, 2013 3:00 PM >> To: users@activemq.apache.org >> Subject: Re: ActiveMQ.DLQ >> >> Barry, >> >> ActiveMQ by default auto-creates destinations as it needs/requires them.= You don't have to define the DLQ explicitly. If a message goes to the Acti= veMQ.DLQ, or if a consumer listens to the ActiveMQ.DLQ queue, then the brok= er will create it. >> >> You can set up queues ahead of time if you'd like, but it's not necessar= y. >> >> >> >> On Thu, Nov 7, 2013 at 11:17 AM, wrote: >>> It is my understanding that expired messages are stored on the ActiveMQ= .DLQ queue. When I start the ActiveMQ broker, I do not see the DLQ defined= . If this is where the expired messages go to, wouldn't it be a default qu= eue for the default configuration? If not, then do I need to define it usi= ng that exact name? What other attributes would I define the queue with? >>> >>> I don't see this queue in my activemq.xml file or any config file out o= f the box... >>> >>> >>> Regards, >>> >>> Barry Barnett >>> WMQ Enterprise Services & Solutions >>> W >>> >>> >>> >> >> >> >> -- >> Christian Posta >> http://www.christianposta.com/blog >> twitter: @christianposta > > > > -- > Christian Posta > http://www.christianposta.com/blog > twitter: @christianposta --=20 Christian Posta http://www.christianposta.com/blog twitter: @christianposta