The qpid broker already does loop-suppression to prevent messages from
taking the same path more than once. The reason you get two messages is
because you have created a topology with redundant paths in it (i.e.
there are two distinct paths from each sender to each receiver). Your
receiver will receive one copy of the message for each distinct path
through the topology. If you expand your broker network with more
redundancy, you will potentially receive many more copies of each message.
The qpid clients do not prevent delivery of duplicate messages. You can
layer such a capability on top of the clients if you wish. The other
thing you can do is to break the loop in your topology (close one of the
federation links) to prevent duplication.
-Ted
On 06/27/2013 05:24 AM, [email protected] wrote:
Hi,
I am using broker federation in qpid 0.20 C++ broker and have a 3
broker topology as attached.
I have configured bidirectional dynamic routes for "amq.direct"
exchange for the 3 brokers as shown attached.
When I publish a message from qpid JMS to 1001 and receive it from
qpid JMS on 10003, I get 2 messages, instead of 1.
Can qpid do duplicate detection and delivery only 1 message ?
Thanks
Rajib
_______________________________________________
This message is for information purposes only, it is not a
recommendation, advice, offer or solicitation to buy or sell a product
or service nor an official confirmation of any transaction. It is
directed at persons who are professionals and is not intended for
retail customer use. Intended for recipient only. This message is
subject to the terms at: www.barclays.com/emaildisclaimer
<http://www.barclays.com/emaildisclaimer>.
For important disclosures, please see:
www.barclays.com/salesandtradingdisclaimer
<http://www.barclays.com/salesandtradingdisclaimer> regarding market
commentary from Barclays Sales and/or Trading, who are active market
participants; and in respect of Barclays Research, including
disclosures relating to specific issuers, please see
http://publicresearch.barclays.com.
_______________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]