[rabbitmq-discuss] .NET client connection shutdown codes

[Simone Busoli]

Hi, I'm trying to figure out what values the ShutdownEventArgs.ReplyCode
property can be assigned by the .NET client.
I started investigating while trying to solve a reconnection problem
whereby the connection was shutdown by the AppDomain unload event handler
and exited with code 0x21d, but noticed there's at least another case in
the code where the ReplyCode is assigned the same value, and it's in the
MainLoop method, in the last chance catch block.
Using same codes for different shutdown reasons makes it difficult to
distinguish different shutdown scenarios, and I would like to avoid relying
on the ReplyText property to discriminate it.
So I'm wondering what is the criteria used by the API to set this value
and, bumping one thread from some time ago, it would be very nice to have
some guidance about how the .NET API behaves when anything goes wrong.
Currently I have to say that it's quite difficult to cope with failure
scenarios because the behavior of the API is difficult to predict, and I am
under the impression that it is somewhat inconsistent in terms of which
exceptions you have to expect to bubble up in different circumstances.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120204/8b254831/attachment.htm>