I should add that currently I create a ConnectionFactory, followed by a connection & model when the client is initialized and reuse this instance from the life of the client.<div><br></div><div>Also when a network connection drops out & comes back online, the publishes start to fail also (usually an AlreadyClosedException with underlying C# socket exceptions). I would like the behaviour to make sure both publishing & subscribing continues to work after a network failure.<br>
<br><div class="gmail_quote">On Wed, Jul 25, 2012 at 11:33 AM, Michael Nye <span dir="ltr"><<a href="mailto:michael.nye1@gmail.com" target="_blank">michael.nye1@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello,<div><br></div><div>I have a C# client connecting to a RabbitMQ server over an unreliable network connection. It is both subscribing to and publishing messages. If the network connection is lost for a period of time and then brought back online, it appears that the subscriptions will not continue to receive messages.</div>
<div><br></div><div>What are the general "best practices" in handling this situation? Is there a simple property I'm missing that will auto-reconnect in these situations? Or must I manually check & reconnect when the network disconnection occurs?</div>
<div><br></div><div>Thanks for any help.</div>
</blockquote></div><br></div>