Return-Path: Delivered-To: apmail-geronimo-activemq-users-archive@www.apache.org Received: (qmail 87903 invoked from network); 25 Jul 2006 21:54:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 25 Jul 2006 21:54:46 -0000 Received: (qmail 76078 invoked by uid 500); 25 Jul 2006 21:54:45 -0000 Delivered-To: apmail-geronimo-activemq-users-archive@geronimo.apache.org Received: (qmail 76066 invoked by uid 500); 25 Jul 2006 21:54:45 -0000 Mailing-List: contact activemq-users-help@geronimo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: activemq-users@geronimo.apache.org Delivered-To: mailing list activemq-users@geronimo.apache.org Received: (qmail 76057 invoked by uid 99); 25 Jul 2006 21:54:45 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Jul 2006 14:54:45 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of lists@nabble.com designates 72.21.53.35 as permitted sender) Received: from [72.21.53.35] (HELO talk.nabble.com) (72.21.53.35) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Jul 2006 14:54:44 -0700 Received: from [72.21.53.38] (helo=jubjub.nabble.com) by talk.nabble.com with esmtp (Exim 4.50) id 1G5UrA-000622-7o for activemq-users@geronimo.apache.org; Tue, 25 Jul 2006 14:54:24 -0700 Message-ID: <5494079.post@talk.nabble.com> Date: Tue, 25 Jul 2006 14:54:24 -0700 (PDT) From: bdiesenhaus To: activemq-users@geronimo.apache.org Subject: Network of Brokers MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-Sender: brian.diesenhaus@ironmountain.com X-Nabble-From: bdiesenhaus X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N We are configuring for n number of front-end broker machines. The idea is for these brokers to bridge traffic from the clients connecting via tcp to the internal system which is connecting via discovery://multicast: 1. What would be the best way to do this? 2. Should we just use static list with failover for the client side? 3. Will activemq work with dns round robin or vips? 4. Can you use the Proxy Connector with Multicast Discovery? See http://www.nabble.com/Proxy-Connectors-and-Multicast-Discovery-tf1998790.html for more details. -- View this message in context: http://www.nabble.com/Network-of-Brokers-tf2000843.html#a5494079 Sent from the ActiveMQ - User forum at Nabble.com.