mklishin at gopivotal.com
Fri Feb 14 21:23:47 GMT 2014
On 15 Feb 2014, at 01:19, Arun Rao <arunrao.seattle at gmail.com> wrote:
> What if you used a TCP loadbalancer and the client cannot talk to a RabbitMQ node? Simply, if the RabbitMQ server crashed, does the Java client code itself catch reason=“shutdown"
Please read http://www.rabbitmq.com/api-guide.html#shutdown.
The AMQP connection and channel share the same general approach to managing network failure, internal failure, and explicit local shutdown.
Those objects always end up in the closed state, regardless of the reason that casued the closure, like an application request, an internal client library failure, a remote network request or network failure.
Connection termination will trigger a shutdown regardless of the reason, whether RabbitMQ had a chance
to send clients connection.close or the OS detected a socket operation error.
Software Engineer, Pivotal/RabbitMQ
More information about the rabbitmq-discuss