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 37DB0974E for ; Sun, 6 Nov 2011 21:30:56 +0000 (UTC) Received: (qmail 47719 invoked by uid 500); 6 Nov 2011 21:30:55 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 47659 invoked by uid 500); 6 Nov 2011 21:30:54 -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 47651 invoked by uid 99); 6 Nov 2011 21:30:54 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 06 Nov 2011 21:30:54 +0000 X-ASF-Spam-Status: No, hits=2.8 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jasonwhaley@gmail.com designates 209.85.161.43 as permitted sender) Received: from [209.85.161.43] (HELO mail-fx0-f43.google.com) (209.85.161.43) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 06 Nov 2011 21:30:49 +0000 Received: by faat9 with SMTP id t9so6013213faa.2 for ; Sun, 06 Nov 2011 13:30:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=91TWvBXvoT4ybcsNez8SmgoXbUdZhPx6dPtKGjOIPBI=; b=X+wm57GnNBg+V8qhmJg5bfmY+rJV7WJwNMJdK6grGmARWli+FQ9RNSjS8ukLw91kXl 7pnhybGEq88iCjLyTMy3O/RCa5YxWr5a9EL1C8DazxMyoOflcb89BRGLEbNgutSZ/ldy 6gqC/qT/8A+wkCIDyeRyRueCuDB6dCUrVPlFw= MIME-Version: 1.0 Received: by 10.223.91.82 with SMTP id l18mr39944346fam.30.1320615027933; Sun, 06 Nov 2011 13:30:27 -0800 (PST) Received: by 10.223.13.4 with HTTP; Sun, 6 Nov 2011 13:30:27 -0800 (PST) In-Reply-To: <1320415442379-3990172.post@n4.nabble.com> References: <1320415442379-3990172.post@n4.nabble.com> Date: Sun, 6 Nov 2011 16:30:27 -0500 Message-ID: Subject: Re: How can I restrict durable consumers From: Jason Whaley To: users@activemq.apache.org Content-Type: multipart/alternative; boundary=000e0ce0cc1ca003fd04b117a530 --000e0ce0cc1ca003fd04b117a530 Content-Type: text/plain; charset=ISO-8859-1 There doesn't appear to be a way to limit this via activemq configuration, at least not from a quick browsing of the schema at http://activemq.apache.org/schema/core/activemq-core-5.5.0-schema.html You may want to consider using virtual topics for this instead. See http://activemq.apache.org/virtual-destinations.html for an overview. Essentially you can have your producer still publish a topic, but your consumers will consume from queues instead and those queues are created dynamically. On Fri, Nov 4, 2011 at 10:04 AM, manua wrote: > Hi, > > I want my broker to not allow durable consumers. > Is there an option/setting in activemq.xml such that no durable consumer > can > be connected to any of its topic. > > Kindly let me know your inputs. > > Thanks > Manu > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/How-can-I-restrict-durable-consumers-tp3990172p3990172.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > --000e0ce0cc1ca003fd04b117a530--