[rabbitmq-discuss] .NET client connection shutdown codes

Steven Taylor taylste at gmail.com
Tue Feb 7 05:10:45 GMT 2012

If you wanted to, the RabbitMQ team could subclass the AQMP error codes.
i.e. treat the AQMP number as the category, and then have a unique cause
numbers underneath these.

Is there any guidance on the site / in PDF on getting subscribers to
reconnect + reponding to these events in a fault tolerant way?  I mean, I /
we can evolve an approach, but if there was a starting point / code
example, that would be really helpful.

btw: recently in debugging, I appreciated that using the same DeliveryTag
twice generated an exception, but I'm not sure that the channel should have
automatically disconnected. Just thought I'd mention it.


On 6 February 2012 10:27, Emile Joubert <emile at rabbitmq.com> wrote:

> Hi Simone,
> On 03/02/12 23:54, Simone Busoli wrote:
> > Hi, I'm trying to figure out what values the ShutdownEventArgs.ReplyCode
> > property can be assigned by the .NET client.
> Thanks for your feedback. There is a relative scarcity of error codes.
> The AMQP specification only defines only a small number, which means
> that some codes have to be re-used. "Precondition failed" (406) is a
> good example of a code that is widely used, so the code alone does not
> identify a unique problem.
> The code in your example is "Internal error" (541). This code should be
> read as an error class and you need to inspect the error message for
> more detail.
> -Emile
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120207/8582571d/attachment.htm>

More information about the rabbitmq-discuss mailing list