Return-Path: 
 <activemq-users-return-1312-apmail-geronimo-activemq-users-archive=geronimo.apache.org@geronimo.apache.org>
Delivered-To: apmail-geronimo-activemq-users-archive@www.apache.org
Received: (qmail 9019 invoked from network); 10 May 2006 13:47:23 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 10 May 2006 13:47:23 -0000
Received: (qmail 70911 invoked by uid 500); 10 May 2006 13:46:36 -0000
Delivered-To: apmail-geronimo-activemq-users-archive@geronimo.apache.org
Received: (qmail 70890 invoked by uid 500); 10 May 2006 13:46:35 -0000
Mailing-List: contact activemq-users-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:activemq-users-help@geronimo.apache.org>
List-Unsubscribe: <mailto:activemq-users-unsubscribe@geronimo.apache.org>
List-Post: <mailto:activemq-users@geronimo.apache.org>
List-Id: <activemq-users.geronimo.apache.org>
Reply-To: activemq-users@geronimo.apache.org
Delivered-To: mailing list activemq-users@geronimo.apache.org
Received: (qmail 70881 invoked by uid 99); 10 May 2006 13:46:35 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 May 2006 06:46:35 -0700
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: domain of xleyba@gmail.com designates
 64.233.162.201 as permitted sender)
Received: from [64.233.162.201] (HELO nz-out-0102.google.com) (64.233.162.201)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 May 2006 06:46:34 -0700
Received: by nz-out-0102.google.com with SMTP id q3so1818815nzb
        for <activemq-users@geronimo.apache.org>;
 Wed, 10 May 2006 06:46:14 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=fzXs+y+me9mKJnWuR9ouYviMUhYGo+t9rgmQ2OgGuiEUOEkrTy1+Y+FB0uAWRTrerExlXCyJz8krAJYDEpsjnaqm5CrW5ScnoWTr9KKDIHudeTaLek+IbWwTFY8F7eeIa9S70EgyFq6OLxkW/QMu10HwsTHDal7bE7Hive1Vn4I=
Received: by 10.65.194.19 with SMTP id w19mr364990qbp;
        Wed, 10 May 2006 06:46:14 -0700 (PDT)
Received: by 10.65.251.10 with HTTP; Wed, 10 May 2006 06:46:14 -0700 (PDT)
Message-ID: <933f2a180605100646w6731972fxe3895f71a7937f86@mail.gmail.com>
Date: Wed, 10 May 2006 15:46:14 +0200
From: "Javier Leyba" <xleyba@gmail.com>
To: activemq-users@geronimo.apache.org
Subject: Re: Network of brokers
In-Reply-To: 
 <001FD7EB9646934B9237F09DE8E1F07C020D0197@DE0-MAILMB02.res.airbus.corp>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: 
 <001FD7EB9646934B9237F09DE8E1F07C020D0197@DE0-MAILMB02.res.airbus.corp>
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

On 5/10/06, Gerdes, Mike <Mike.Gerdes@airbus.com> wrote:
>
> hi,
>
> hm from my knowledge your answer is incorrect or maybe I misunderstood yo=
u.
>
> You configure your local broker, your output and recieving broker with th=
e transport connector. Your network connector defines the brokers where you=
 want to connect to. If you have defined more then adress in your static at=
tribute, then the broker will connect to all of them.
>
> failover is similar to static, but with the difference that your broker w=
ill connect to the first broker and when that one is not available it switc=
hes to the next and so on.
>
> I think the example at http://www.activemq.com/Static+Transport+Reference=
 is a bit misleading, because you connect there to your local broker as wel=
l as to a remote broker.


Ouch, may you didn't understood me.

Some time ago James told me this:

----------

Now the <networkConnector> is an outbound connection, a way for a broker to
talk to other brokers. So URIs used inside here will be used to create
client connections to other brokers. So for the network to be established,
there must be brokers out there listening (via the <transportConnector>) on
the URIs mentioned in the <networkConnector>
--------

Then, the first host:port that you pass as parameter in the network
connector is the host:port that you are configuring but with a port
number different from transport connector, and then you must declare
all the host you want to connect this broker to with their transport
ports.

This is what I've been trying to say...  :)

J



--
Javier Leyba
Barcelona - Spain
http://blog.leyba.com.ar