<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Simone,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Ah, sorry I missed the suggestion to configure a fully interconnected network.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Yes that would work. However it becomes an administrative nightmare as nodes are added to the network.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Therefore I don’t think this is viable.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>-John<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Busoli, Simone [mailto:Simone.Busoli@ferrari.com] <br><b>Sent:</b> Wednesday, January 04, 2012 7:02 AM<br><b>To:</b> Letourneau, John P (John); Simone Busoli<br><b>Cc:</b> rabbitmq-discuss@lists.rabbitmq.com<br><b>Subject:</b> RE: [rabbitmq-discuss] Federation Configuration and Duplicate Messages<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>That’s true with your current configuration, but if you federate each broker with the other two like I suggested it is going to work.</span><o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='margin-left:.5in'><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Letourneau, John P (John) [mailto:john.letourneau@alcatel-lucent.com] <br><b>Sent:</b> mercoled� 4 gennaio 2012 12:54<br><b>To:</b> Simone Busoli<br><b>Cc:</b> Busoli, Simone; rabbitmq-discuss@lists.rabbitmq.com<br><b>Subject:</b> RE: [rabbitmq-discuss] Federation Configuration and Duplicate Messages</span><o:p></o:p></p></div></div><p class=MsoNormal style='margin-left:.5in'> <o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Simone,</span><o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>If I were to set hops=1, then a message posted at N1 would go to N2 but will NOT go to N3. This has been verified.</span><o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Similarly a message posted at N3 would go to N2 but NOT go to N1.</span><o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>-John</span><o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='margin-left:.5in'><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Simone Busoli [mailto:simone.busoli@gmail.com] <br><b>Sent:</b> Tuesday, January 03, 2012 3:16 PM<br><b>To:</b> Letourneau, John P (John)<br><b>Cc:</b> Busoli, Simone; rabbitmq-discuss@lists.rabbitmq.com<br><b>Subject:</b> Re: [rabbitmq-discuss] Federation Configuration and Duplicate Messages</span><o:p></o:p></p></div><p class=MsoNormal style='margin-left:.5in'> <o:p></o:p></p><p style='margin-left:.5in'>Inline<o:p></o:p></p><p style='margin-left:.5in'>On Jan 3, 2012 4:52 PM, "Letourneau, John P (John)" <<a href="mailto:john.letourneau@alcatel-lucent.com">john.letourneau@alcatel-lucent.com</a>> wrote:<br>><br>> Well, perhaps a bit more about my configuration 8-)<br>><br>> 3 nodes…call them N1, N2, N3.<br>><br>> On each I have federation configured.<br>><br>> N2 – exchange log, connects to N1/log and N3/log<br>><br>> N3 – exchange log, connects to N2/log<br>><br>> Right now I cannot seem to have the N1 exchange log connect to N2/log; will need to find out why sometime.<br>><br>> I do it this way so that regardless of where the producer of the log message is, everyone everywhere will see it.<o:p></o:p></p><p style='margin-left:.5in'>If this is your aim, can't you simply federate the log exchange on each broker with the other two and set max hops to 1?<o:p></o:p></p><p style='margin-left:.5in'>><br>> <br>><br>> Each layer in the hierarchy only knows about nodes in adjacent layers…N2 being the busy one with a layer above and below.<br>><br>> If everyone has hops=1, sending a log message to N1/log will only go to N2 and not N3 [this is correct].<br>><br>> Setting hops=4, sending a log to N1/log will go to N2 and N3…it will also be returned to N2 thus a consumer on N2 will see the original msg AND the one sent via N2/N3 federation link. Also N3 sees it twice also for a total of once on N1, twice on N2, and twice on N3…the message took a total of 4 hops.<br>><br>> <br>><br>> So, this is what I mean by ‘one might expect’ 8-)<br>><br>> -John<br>><br>> <br>><br>> From: Busoli, Simone [mailto:<a href="mailto:Simone.Busoli@ferrari.com">Simone.Busoli@ferrari.com</a>] <br>> Sent: Tuesday, January 03, 2012 10:23 AM<br>> To: Letourneau, John P (John); <a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>> Subject: RE: Federation Configuration and Duplicate Messages<br>><br>> <br>><br>> Hi John, I’m not sure about this:<br>><br>> <br>><br>> As one might expect, this sometimes results in the message being seen >1 time at some clients.<br>><br>> <br>><br>> It shouldn’t be the expected behavior except for certain scenarios (i.e. disconnection of the brokers). Am I missing something perhaps?<br>><br>> _________________________________________________________________________________________________________________<br>> Questo messaggio e da intendersi esclusivamente ad uso del destinatario e puo contenere informazioni che sono di natura privilegiata, confidenziale<br>> o non divulgabile secondo le leggi vigenti. Se il lettore del presente messaggio non e il destinatario designato, o il dipendente/agente responsabile<br>> per la consegna del messaggio al destinatario designato, si informa che ogni disseminazione, distribuzione o copiatura di questa comunicazione e <br>> strettamente proibita anche ai sensi del decreto legislativo 196/03 . Se avete ricevuto questo messaggio per errore, vi preghiamo di notificarcelo<br>> immediatamente a mezzo e-mail di risposta e successivamente di procedere alla cancellazione di questa e-mail e relativi allegati dal vostro sistema.<br>> _________________________________________________________________________________________________________________<br>> This message is intended only for the use of the addressee and may contain information that is privileged, confidential and exempt from <br>> disclosure under applicable law. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the <br>> message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly <br>> prohibited. If you have received this e-mail in error, please notify us immediately by return e-mail and delete this e-mail and all attachments from <br>> your system.<br>> _________________________________________________________________________________________________________________<br>><br>><br>> _______________________________________________<br>> rabbitmq-discuss mailing list<br>> <a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>> <a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>><o:p></o:p></p><p><span style='font-size:7.5pt'>_________________________________________________________________________________________________________________<br>Questo messaggio � da intendersi esclusivamente ad uso del destinatario e pu� contenere informazioni che sono di natura privilegiata, confidenziale<br>o non divulgabile secondo le leggi vigenti. Se il lettore del presente messaggio non � il destinatario designato, o il dipendente/agente responsabile<br>per la consegna del messaggio al destinatario designato, si informa che ogni disseminazione, distribuzione o copiatura di questa comunicazione � <br>strettamente proibita anche ai sensi del decreto legislativo 196/03 . Se avete ricevuto questo messaggio per errore, vi preghiamo di notificarcelo<br>immediatamente a mezzo e-mail di risposta e successivamente di procedere alla cancellazione di questa e-mail e relativi allegati dal vostro sistema.<br>_________________________________________________________________________________________________________________<br>This message is intended only for the use of the addressee and may contain information that is privileged, confidential and exempt from <br>disclosure under applicable law. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the <br>message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly <br>prohibited. If you have received this e-mail in error, please notify us immediately by return e-mail and delete this e-mail and all attachments from <br>your system.<br>_________________________________________________________________________________________________________________</span><o:p></o:p></p></div></body></html>