[rabbitmq-discuss] Client on unreliable network best practice?
michael.nye1 at gmail.com
Wed Jul 25 03:53:57 BST 2012
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.
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.
On Wed, Jul 25, 2012 at 11:33 AM, Michael Nye <michael.nye1 at gmail.com>wrote:
> 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
> 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?
> Thanks for any help.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss