Hi,<div><br></div><div>So you finally recommend to set a policy ha-mode all on the�<span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">queue created in the upstream exchange's broker, like I did ?</span></div>
<div><br></div><div><span style="color:rgb(34,34,34);font-family:arial,sans-serif">The test is very simple. I send 200 000 messages on the upstream exchange with a connection factory with both nodes and a retry timer (like in the Spring Rabbit AmqpAppender).</span></div>
<div><span style="color:rgb(34,34,34);font-family:arial,sans-serif">I receive all messages on the downstream queue and verify that each sent message has been received.</span></div><div><span style="color:rgb(34,34,34);font-family:arial,sans-serif">During the test, I shutdown and restart upstream node.</span></div>
<div><span style="color:rgb(34,34,34);font-family:arial,sans-serif"><br></span></div><div><span style="color:rgb(34,34,34);font-family:arial,sans-serif">But you are right, I do not use publisher confirm.</span></div><div>
<span style="color:rgb(34,34,34);font-family:arial,sans-serif">I probably hit the "unsynchronized queue" problem.</span></div><div><br></div><div><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">Otherwise, do you think that my setup is correct to make sure that t</span><span style="background-color:rgb(255,255,255);color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px">he messages will arrive at the downstream exchange, not duplicated and without loss</span><span style="background-color:rgb(255,255,255);color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px">�(</span><span style="color:rgb(34,34,34);font-family:arial,sans-serif">publisher confirm excepted) ?</span></div>
<div><br></div><div><font color="#222222" face="arial, sans-serif">Regards,</font></div><div><font color="#222222" face="arial, sans-serif">Vladislav</font></div><div><br><div class="gmail_quote">2012/12/28 Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@rabbitmq.com" target="_blank">matthias@rabbitmq.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Vladislav,<div class="im"><br>
<br>
On 28/12/12 09:32, Vladislav Pernin wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
{{shutdown,{server_initiated_<u></u>close,404,<br>
� � � � � � � � � � � � � � � � � � <<"NOT_FOUND - home node<br>
'rabbit@remote-server1' of durable queue 'federation: upstream-exchange<br>
-> federation-local:downstream-<u></u>exchange' in vhost '/' is down or<br>
inaccessible">>}},<br>
</blockquote>
<br></div>
That happens because the queue used by federation is durable but not mirrored, so when the node on which it was created goes down it is no longer accessible.<br>
<br>
You said you tried making that queue mirrored, but that resulted in message loss. How did you detect the message loss? Does the upstream publisher have confirms enabled? If it received a confirmation for a message then I certainly would expect the message to eventually make it to the downstream. In the absence of such confirmation all bets are off.<br>
<br>
Regards,<br>
<br>
Matthias.<br>
</blockquote></div><br></div>