This is where the "mandatory" feature comes in.<br><br>1. Declare your queue as durable.<br>2. Send your RPC requests with "mandatory" flag.<br><br>Then:<br><ul><li>if rabbitmq is down, the RPC client won't be able to connect. Clear.</li>
<li>if rabbitmq is up, but the RPC server is down, and noone has created the queue yet, then the request will be Basic.Return'd to you. Also clear.</li><li>if rabbitmq is up, but the RPC server is down, and the queue was previously created by somebody, then the request will be enqueued. As long as the RPC server returns to service in a timely way, everyone's happy.</li>
<li>if rabbitmq is up, and the RPC server is up, normal service ensues.</li></ul><p>Regards,<br> Tony</p><p><br></p><br><div class="gmail_quote">On 2 December 2011 09:21, Alex Grönholm <span dir="ltr"><<a href="mailto:alex.gronholm@nextday.fi">alex.gronholm@nextday.fi</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">That was the plan from the start, but I wanted to cover cases where something goes wrong (server starts with rabbitmq but not the rpc server) in which case the client would be stuck waiting forever.<br>
But I guess that dead lettering feature will fix that.<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" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
<br></blockquote></div><br>