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 BD3FF10274 for ; Fri, 8 Nov 2013 17:44:24 +0000 (UTC) Received: (qmail 45228 invoked by uid 500); 8 Nov 2013 17:44:14 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 45132 invoked by uid 500); 8 Nov 2013 17:44:09 -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 44911 invoked by uid 99); 8 Nov 2013 17:43:56 -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:43:56 +0000 X-ASF-Spam-Status: No, hits=-5.0 required=5.0 tests=RCVD_IN_DNSWL_HI,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of barry.barnett@wellsfargo.com designates 151.151.26.138 as permitted sender) Received: from [151.151.26.138] (HELO mxdcmv02i.wellsfargo.com) (151.151.26.138) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Nov 2013 17:43:51 +0000 Received: from mxicmv01.wellsfargo.com (mxicmv01.wellsfargo.com [10.91.24.71]) by mxdcmv02i.wellsfargo.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id rA8HhUHs023623 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Fri, 8 Nov 2013 17:43:30 GMT DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=wellsfargo.com; s=2011-05-wfb; t=1383932611; bh=IXbN9HSTccD8DWk6Kbrp56eu6ilbs/mC4Mhdac7KdYA=; h=From:To:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=bjB83IqlktjybuJgh28gP7MvFeJEf6PhrPtl6f25jGElquJ51uf9cRN4N8s5GFAEj tGB/XO0Sr7jTTnQcrSJsLhWVtDkhziuQMh8hJnqgNdDjlDbnqOc+01bGx0JKdx+kKE L+AcdgtNbkdYa5zX82qi49q4izyWER+zLi9x5RHQ= Received: from MSGEXSV27119.ent.wfb.bank.corp (msgexsv27119.wellsfargo.com [162.101.144.44]) by mxicmv01.wellsfargo.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id rA8HhTq0002705 for ; Fri, 8 Nov 2013 17:43:30 GMT Received: from MSGEXSV21106.ent.wfb.bank.corp ([169.254.6.212]) by MSGEXSV27119.ent.wfb.bank.corp ([162.101.144.44]) with mapi id 14.02.0347.000; Fri, 8 Nov 2013 11:43:29 -0600 From: To: Subject: RE: ActiveMQ.DLQ Thread-Topic: ActiveMQ.DLQ Thread-Index: Ac7b5Ztaxt0zORNZQwGES1+ReHA9KwAQJK0AABb602AAEL0iAAAJhgog///cCwCAAF5p8A== Date: Fri, 8 Nov 2013 17:43:29 +0000 Message-ID: <443BCE38E921434394B45FF0813FA578053DA4E2@MSGEXSV21106.ent.wfb.bank.corp> References: <443BCE38E921434394B45FF0813FA578053D96F0@MSGEXSV21106.ent.wfb.bank.corp> <443BCE38E921434394B45FF0813FA578053DA10C@MSGEXSV21106.ent.wfb.bank.corp> <443BCE38E921434394B45FF0813FA578053DA484@MSGEXSV21106.ent.wfb.bank.corp> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.91.43.136] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org So there must be some code written in the broker to dynamically create that= queue then, correct? And other system type queues? Regards, Barry Barnett WMQ Enterprise Services & Solutions Wells Fargo Cell: 704-564-5501 -----Original Message----- From: Christian Posta [mailto:christian.posta@gmail.com]=20 Sent: Friday, November 08, 2013 12:21 PM To: users@activemq.apache.org Subject: Re: ActiveMQ.DLQ Well, it would be the same as a user-queue... ie.. if something tries to se= nd to the DLQ, it will be auto-created. So for example, when the broker che= cks 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 (i= t's not on a fresh broker install, for example), then it will be auto-creat= ed 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=20 > either by calling createQueue() or createTopic() on a JMS Session=20 > creating an instance of ActiveMQTopic or ActiveMQQueue and possibly=20 > registering 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 -- Christian Posta http://www.christianposta.com/blog twitter: @christianposta