Return-Path: Delivered-To: apmail-geronimo-activemq-users-archive@www.apache.org Received: (qmail 77892 invoked from network); 23 May 2006 02:36:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 23 May 2006 02:36:07 -0000 Received: (qmail 20420 invoked by uid 500); 23 May 2006 02:36:06 -0000 Delivered-To: apmail-geronimo-activemq-users-archive@geronimo.apache.org Received: (qmail 20402 invoked by uid 500); 23 May 2006 02:36:06 -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 20393 invoked by uid 99); 23 May 2006 02:36:06 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 May 2006 19:36:06 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [208.176.63.109] (HELO localhost.ldsys.net) (208.176.63.109) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 May 2006 19:36:04 -0700 Received: from [10.0.2.2] (adsl-71-143-209-211.dsl.chcgil.sbcglobal.net [71.143.209.211]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by localhost.ldsys.net (Postfix) with ESMTP id D6FB64644E for ; Mon, 22 May 2006 21:38:47 -0500 (CDT) Message-ID: <447274FA.9000203@ldsys.net> Date: Mon, 22 May 2006 21:35:38 -0500 From: "Christopher G. Stach II" User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: activemq-users@geronimo.apache.org Subject: Re: broker/discovery client help References: <20060523021614.60279.qmail@web53612.mail.yahoo.com> In-Reply-To: <20060523021614.60279.qmail@web53612.mail.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Paul Tomsic wrote: > thanks for the information. > i think i'm confused, though, as to how > consumers/producers would specify a specific cluster > and a machine? > > so say i've got consumers/producers in china that need > to connect to a cluster running in chicago named > "foo". > I've also got another cluster of brokers in chicago > running as "bar" > > how would the consumers/producers specify which > cluster to connect to? > > would my consumers connect as > > "discovery:multicast://chicago.mycompany.com/foo" > > -and- > > "discovery:multicast://chicago.mycompany.com/bar" > > ?? > > thanks again for the help.. > > paul > They subscribe to the same multicast group, your multicast routers would forward the packets, and as long as the TTLs are high enough, they would reach the other side. http://www.google.com/search?hl=en&q=ip+multicast+routing Since you said you have two "clusters", maybe you should just set up unicast TCP connectors and use those. Unless you have a bunch of machines in each group, or they're very dynamic and changing, maybe discovery isn't even the ideal setup. -- Christopher G. Stach II