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 A6790CAA8 for ; Wed, 10 Dec 2014 00:09:32 +0000 (UTC) Received: (qmail 60737 invoked by uid 500); 10 Dec 2014 00:09:32 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 60691 invoked by uid 500); 10 Dec 2014 00:09:32 -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 60680 invoked by uid 99); 10 Dec 2014 00:09:31 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Dec 2014 00:09:31 +0000 X-ASF-Spam-Status: No, hits=2.9 required=5.0 tests=SPF_SOFTFAIL,URI_HEX,URI_TRY_3LD X-Spam-Check-By: apache.org Received-SPF: softfail (nike.apache.org: transitioning domain of alex.zdvorak@gmail.com does not designate 162.253.133.43 as permitted sender) Received: from [162.253.133.43] (HELO mwork.nabble.com) (162.253.133.43) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Dec 2014 00:09:05 +0000 Received: from mjoe.nabble.com (unknown [162.253.133.57]) by mwork.nabble.com (Postfix) with ESMTP id 6DEF8D2EE6C for ; Tue, 9 Dec 2014 16:09:04 -0800 (PST) Date: Tue, 9 Dec 2014 16:00:41 -0800 (PST) From: azdvorak To: users@activemq.apache.org Message-ID: <1418169641254-4688631.post@n4.nabble.com> In-Reply-To: References: <1418079418092-4688578.post@n4.nabble.com> <1418148843841-4688623.post@n4.nabble.com> Subject: Re: Reply message not forwarded across temporary bridged destination MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Thank you for your input so far, it has been helpful. Although I was able to verify including all destinations (via wildcard) does indeed bridge temporary destinations, I do not believe this is the intended solution for the following reasons: 1) temp destinations are created dynamically and use the BrokerID in the name, so having to specify a queue in is not intuitive. If there is a temp destination prefix that can be used that would be helpful and I could use that for now. 2) The second reason being: There is a configuration option "bridgeTempDestinations" set on the NetworkConnector as documented here http://activemq.apache.org/networks-of-brokers.html This is set to "true" by default and leads me to believe this is the proper way to bridge temporary destinations. Furthermore when I set this to false I do not see the destination created on both brokers. Where as if I set the value to true, I can see the destination instantiated in both broker logs. If anyone has additional insight I would greatly appreciate it. Thanks again. -- View this message in context: http://activemq.2283324.n4.nabble.com/Reply-message-not-forwarded-across-temporary-bridged-destination-tp4688578p4688631.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.