Mailing-List: contact users-help@qpid.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@qpid.apache.org
MIME-Version: 1.0
Date: Thu, 28 Jan 2016 13:02:16 -0600
Message-ID: 
 <CAL1zMnPWYQyYYyPssDZivCs7haMRfFvhZ4-ctfmBuOYw1NKq=A@mail.gmail.com>
Subject: federated broker system with duplicate routes - no message
 duplication observed
From: jjw tectec <jjw.tectec@gmail.com>
To: users@qpid.apache.org
Content-Type: multipart/related; boundary=001a1140f866a8d234052a698ec1

--001a1140f866a8d234052a698ec1
Content-Type: multipart/alternative; boundary=001a1140f866a8d232052a698ec0

--001a1140f866a8d232052a698ec0
Content-Type: text/plain; charset=UTF-8

I've set up a simple 4-broker system, where between Bs (source broker) and
Bd (destination broker) are two middle brokers set up in parallel, like
this:

[image: Inline image 1]

The script that I used to set up all the resources & routes is shown at the
end of this message.
I attached a publisher to Bs and attached 3 subscribers to the other 3
brokers.
What I was expecting to see was all 3 brokers should see messages.
The actual observation was: Only B1 and Bf received messages. B2 never
received messages, even when B1 was down.

route map showed that all broker connections were set up as expected, but
why would only the first route work and not the other? (I have added more
brokers B3 B4... into the test, always, only the first established route
would work.) Please help.


Thanks

jjw

----------------------script used for setting up the broker
network-------------------------------

~/qpid/qpid-tools-0.32/src/py/qpid-config -a $Bs add queue $QUEUE --durable
~/qpid/qpid-tools-0.32/src/py/qpid-config -a $B1 add queue $QUEUE --durable
~/qpid/qpid-tools-0.32/src/py/qpid-config -a $B2 add queue $QUEUE --durable

~/qpid/qpid-tools-0.32/src/py/qpid-config -a $B1 add exchange topic $EX
--durable
~/qpid/qpid-tools-0.32/src/py/qpid-config -a $B2 add exchange topic $EX
--durable
~/qpid/qpid-tools-0.32/src/py/qpid-config -a $Bd add exchange topic $EX
--durable

~/qpid/qpid-tools-0.32/src/py/qpid-config -a $B1 bind $EX $QUEUE $QUEUE
--durable
~/qpid/qpid-tools-0.32/src/py/qpid-config -a $B2 bind $EX $QUEUE $QUEUE
--durable

~/qpid/qpid-tools-0.32/src/py/qpid-route -v -d queue add $B1 $Bs $EX $QUEUE
~/qpid/qpid-tools-0.32/src/py/qpid-route -v -d queue add $Bd $B1 $EX $QUEUE
~/qpid/qpid-tools-0.32/src/py/qpid-route -v -d queue add $B2 $Bs $EX $QUEUE
~/qpid/qpid-tools-0.32/src/py/qpid-route -v -d queue add $Bd $B2 $EX $QUEUE

--001a1140f866a8d232052a698ec0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>I&#39;ve set up a simple 4-broker system, where betwe=
en Bs (source broker) and Bd (destination broker) are two middle brokers se=
t up in parallel, like this:</div><div><br></div><div><img src=3D"cid:ii_15=
28983ee9995281" alt=3D"Inline image 1" width=3D"241" height=3D"132"><br></d=
iv><div><br></div><div>The script that I used to set up all the resources &=
amp; routes is shown at the end of this message.</div><div>I attached a pub=
lisher to Bs and attached 3 subscribers to the other 3 brokers.</div><div>W=
hat I was expecting to see was all 3 brokers should see messages.</div><div=
>The actual observation was: Only B1 and Bf received messages. B2 never rec=
eived messages, even when B1 was down.</div><div><br></div><div>route map s=
howed that all broker connections were set up as expected, but why would on=
ly the first route work and not the other? (I have added more brokers B3 B4=
... into the test, always, only the first established route would work.) Pl=
ease help.</div><div><br></div><div><br></div><div>Thanks</div><div><br></d=
iv><div>jjw</div><br><div>----------------------script used for setting up =
the broker network-------------------------------</div><div><br></div><div>=
<div>~/qpid/qpid-tools-0.32/src/py/qpid-config -a $Bs add queue $QUEUE --du=
rable</div><div>~/qpid/qpid-tools-0.32/src/py/qpid-config -a $B1 add queue =
$QUEUE --durable</div><div>~/qpid/qpid-tools-0.32/src/py/qpid-config -a $B2=
 add queue $QUEUE --durable</div><div><br></div><div>~/qpid/qpid-tools-0.32=
/src/py/qpid-config -a $B1 add exchange topic $EX --durable</div><div>~/qpi=
d/qpid-tools-0.32/src/py/qpid-config -a $B2 add exchange topic $EX --durabl=
e</div><div>~/qpid/qpid-tools-0.32/src/py/qpid-config -a $Bd add exchange t=
opic $EX --durable</div><div><br></div><div>~/qpid/qpid-tools-0.32/src/py/q=
pid-config -a $B1 bind $EX $QUEUE $QUEUE --durable</div><div>~/qpid/qpid-to=
ols-0.32/src/py/qpid-config -a $B2 bind $EX $QUEUE $QUEUE --durable</div><d=
iv><br></div><div>~/qpid/qpid-tools-0.32/src/py/qpid-route -v -d queue add =
$B1 $Bs $EX $QUEUE</div><div>~/qpid/qpid-tools-0.32/src/py/qpid-route -v -d=
 queue add $Bd $B1 $EX $QUEUE</div><div>~/qpid/qpid-tools-0.32/src/py/qpid-=
route -v -d queue add $B2 $Bs $EX $QUEUE</div><div>~/qpid/qpid-tools-0.32/s=
rc/py/qpid-route -v -d queue add $Bd $B2 $EX $QUEUE</div></div><div><br></d=
iv></div>

--001a1140f866a8d232052a698ec0--

--001a1140f866a8d234052a698ec1--