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 2F80817C4E for ; Tue, 10 Feb 2015 23:13:23 +0000 (UTC) Received: (qmail 26961 invoked by uid 500); 10 Feb 2015 23:13:22 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 26911 invoked by uid 500); 10 Feb 2015 23:13: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 26900 invoked by uid 99); 10 Feb 2015 23:13:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Feb 2015 23:13:22 +0000 X-ASF-Spam-Status: No, hits=1.3 required=5.0 tests=URI_HEX,URI_TRY_3LD X-Spam-Check-By: apache.org Received-SPF: error (nike.apache.org: local policy) Received: from [162.253.133.43] (HELO mwork.nabble.com) (162.253.133.43) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Feb 2015 23:12:55 +0000 Received: from mjoe.nabble.com (unknown [162.253.133.57]) by mwork.nabble.com (Postfix) with ESMTP id 6D88A137E3BD for ; Tue, 10 Feb 2015 15:11:34 -0800 (PST) Date: Tue, 10 Feb 2015 15:05:45 -0800 (PST) From: artnaseef To: users@activemq.apache.org Message-ID: <1423609545040-4691303.post@n4.nabble.com> In-Reply-To: References: <54CFFC0F.5000901@gmail.com> <81431FCC-F0CF-4E3A-BD54-F41638FC4D84@gmail.com> <1422984686936-4690946.post@n4.nabble.com> Subject: =?UTF-8?Q?Re:_Sending_directly_to_a_queue_doesn=E2=80=99t_?= =?UTF-8?Q?raise_ActiveMQ.Advisory.Producer.Queue.>?= MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org The advisories are very interesting and custom; they are not regular Topics. For example, creating a consumer on one broker in a network of brokers may or may not result in a consumer advisory on other brokers depending on things like the conduitSubscriptions setting. Using an application-specific Topic is a good way to go for event notifications like this. BTW - on the "producer doesn't get created on the target destination" comment - perhaps I should have said, "the producer is never registered as a producer on the target destination". The producer is created, and it sends a message to the target destination, but it is not "associated with" the target destination. Since the producer-creation advisories are destination-specific, that makes it hard to send a producer creation advisory, which would only be feasible at send-time since that's the first time the destination is known. This is one of those finer points of JMS - consumers must be tied to destinations all the time, but producers can decide a destination on every message send. -- View this message in context: http://activemq.2283324.n4.nabble.com/Sending-directly-to-a-queue-doesn-t-raise-ActiveMQ-Advisory-Producer-Queue-tp4690888p4691303.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.