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

Jonathan Halterman jhalterman at gmail.com
Tue Oct 15 23:56:49 BST 2013

Hey Michael,

Yea, you can reproduce both items by attempting to declare a consumer on a
non-existent queue twice in a row. The first invocation closes the channel
and throws an IOException. The second invocation throws an
AlreadyClosedException, though the hardError and initiatedByApplication
flags don't match those from the initial failure.

- jonathan

On Tue, Oct 15, 2013 at 3:45 PM, Michael Klishin <mklishin at gopivotal.com>wrote:

> On oct 16, 2013, at 1:24 a.m., Jonathan Halterman <jhalterman at gmail.com>
> wrote:
> > I noticed that AlreadyClosedException always sets hardError and
> initiatedByApplication to true, even if the error was not hard (only the
> channel was closed) and the channel was not closed by the application. This
> makes it more difficult to properly recover a closed resource if I can't
> easily determine which resource was closed and why. Could this be fixed?
> Jonathan,
> This indeed sounds like a bug.
> How can we reproduce it? Simply attempt an operation on a closed channel?
> Does it matter how exactly the channel was closed?
> MK
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20131015/b63868ca/attachment.htm>

More information about the rabbitmq-discuss mailing list