[rabbitmq-discuss] AlreadyClosedException always sets hardError and initiatedByApplication to true

[Jonathan Halterman]

What Steve mentioned above is that subsequent attempts to use the closed
channel are hard errors that close the connection. This is what I haven't
seen.


On Mon, Oct 21, 2013 at 1:26 PM, Michael Klishin <mklishin at gopivotal.com>wrote:

> On 22 Oct 2013, at 00:17, Jonathan Halterman <jhalterman at gmail.com> wrote:
>
> > After declaring a consumer on a non-existent queue several times, the
> connection is still in tact even though the AlreadyClosedException
> indicates a connection closure
>
> Consuming from a non-existent queue should result in a channel exception
> which closes the channel, not the connection.
>
> MK
> _______________________________________________
> 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/20131021/e71db4af/attachment.htm>