[rabbitmq-discuss] Connection Problem with .NET Client v3.0.4

[David Priddle]

We’ve been having occasional problems with connection errors using the 
Rabbit .NET Client v3.0.4. This manifests itself initially with the error:

Shutting down connection. Reason: AMQP close-reason, initiated by Peer, 
code=503, text="COMMAND_INVALID - second 'channel.open' seen", classId=20, 
methodId=10, cause=

We attempt to Dispose the connection object at this point to make sure 
we’ve released all resources, but get an ObjectDisposedException from the 
underlying NetworkStream. We then attempt to reconnect and start consuming 
again, but although the connection and channels appear to create 
successfully we don’t receive messages off the queue.

I believe the underlying connection we are using is in a bad state.

I’ve noticed some other discussions online about a problem where a 
duplicate channel number may be allocated. I see that the only difference 
between the .NET 3.1.1 client and the 3.0.4 client is a fix has been made 
to the way the IntAllocator class allocates integers. I assume that is this 
bug in the release notes:

.NET client

-------------

bug fixes

25558 fix a bug that could lead to duplicate channel IDs being allocated,causing a connection failure 

Do you have any more information about this bug? Do you think this fix 
would be relevant to the problems we are seeing? Is there any 

(I’m considering whether we should urgently patch our software to upgrade 
us onto 3.1.1 client.)

Best Regards,

David Priddle

 

 

 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130612/efa27a6e/attachment.htm>