[rabbitmq-discuss] BrokerUnreachableException on specific thread after node goes down

Tue Feb 25 15:58:21 GMT 2014

Michael Klishin <mklishin at ...> writes:

> 
> 
> On 25 Feb 2014, at 13:40, Patrick Long <pat at ...> wrote:
> 
> > As an example threads 1 and 2 will both catch separate instances of 
AlreadyClosedException and reset
> their IModel. Next time around Thread 1 will reconnect its Model and start 
dequeueing but Thread 2 will get
> a BrokerUnreachableException. I have tried retrying that reconnect with 
some Thread.Sleep delays and
> it does not help. Once "broken" that thread gets 
BrokerUnreachableException every time.
> > 
> > Any ideas as to why this might be?
> 
> This sounds like a shutdown protocol issue in the .NET client. Can you 
post a small code example
> that reproduces the problem most of the time?
> 
> Thank you.
> 
> MK
> 
> Software Engineer, Pivotal/RabbitMQ
> 
> 

The text in the exception does mention Protocols. It says

"endpoint=amqp-0-9://10.206.20.166:5672, attempts=1
RabbitMQ.Client.Exceptions.ProtocolVersionMismatchException: AMQP server 
protocol negotiation failure: server version unknown-unknown, client version 
0-9"