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 1DB3410571 for ; Sat, 1 Mar 2014 00:10:19 +0000 (UTC) Received: (qmail 94439 invoked by uid 500); 1 Mar 2014 00:10:18 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 94403 invoked by uid 500); 1 Mar 2014 00:10:18 -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 94395 invoked by uid 99); 1 Mar 2014 00:10:17 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Mar 2014 00:10:17 +0000 X-ASF-Spam-Status: No, hits=0.6 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.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; Sat, 01 Mar 2014 00:10:12 +0000 Received: by mail-la0-f51.google.com with SMTP id pv20so2377264lab.24 for ; Fri, 28 Feb 2014 16:09:52 -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; bh=/gfvHVHKbFWaI+tMPaXAzGD8BN9YaDKTzwKkEQn8cHY=; b=xYDYXnB1MRk3VcTZmyx1UQuzvakUJi7/qIaxgIAPz3HUe4SALFsHa7xvWghnCLDzXW I+IooDKvdJSBVx9oSoxAvV+fyRYm3PuMnn+gOR+FU5ysbX1Pc4UfPI7VFq7ti0cCxzI6 FCJdaJEPFtyryDLLpC8s/W7g9/Rkhf8gLwRT6bbOpFp5EPiHThdHbjGX66ALOex301aF 5poJyuc1Fh4ykDNNFggOuuvD1mcZN1lUppfkaZVj+/DeBgFde4keZA8FvlsZysWZcFM9 f2FyGDCyUN7lHwiMfigLIyrL8OxxYeqGHMjdh3I7uOoPQQ9oBulC8hONqhQXDJQggwq8 iE/Q== MIME-Version: 1.0 X-Received: by 10.112.137.137 with SMTP id qi9mr12627520lbb.36.1393632592227; Fri, 28 Feb 2014 16:09:52 -0800 (PST) Received: by 10.114.1.174 with HTTP; Fri, 28 Feb 2014 16:09:52 -0800 (PST) In-Reply-To: <1393400146394-4678360.post@n4.nabble.com> References: <1392211535034-4677863.post@n4.nabble.com> <1392215870348-4677867.post@n4.nabble.com> <1393400146394-4678360.post@n4.nabble.com> Date: Fri, 28 Feb 2014 17:09:52 -0700 Message-ID: Subject: Re: Disable advisory for ActiveMQ broker From: Christian Posta To: "users@activemq.apache.org" Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org No. You have to disable advisory support, and the jms.watchTopicAdvisories=false needs to go on the client (or you can setWatchTopicAdvisories(false) on the connectionFactory). You may also want to disable creation of advisory topics via ActiveMQ authorization security to enforce this policy (although if your clients don't use the above config, they will fail to authorize.. which is what it sounds like you want) On Wed, Feb 26, 2014 at 12:35 AM, khandelwalanuj wrote: > Hi, > > I tried setting connection URI in broker config as: > * > > uri="tcp://0.0.0.0:61616?jms.watchTopicAdvisories=false" /> > > * > > but still it is creating advisories for tmp topics. But when I changed > configuration on client side and make "watchTopicAdvisories=false" in client > consiguration, I can avoid tmp advisories. > > Is there a way to disable tmp topic advisories by making changes in broker > config only ? Because I cannot touch clients source code. > > Thanks, > Anuj > > > > -- > View this message in context: http://activemq.2283324.n4.nabble.com/Disable-advisory-for-ActiveMQ-broker-tp4677863p4678360.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- Christian Posta http://www.christianposta.com/blog twitter: @christianposta