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

• Previous message: [rabbitmq-discuss] rabbitmq client timeouts, slow responses
• Next message: [rabbitmq-discuss] AlreadyClosedException always sets hardError and initiatedByApplication to true
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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?

Cheers,
Jonathan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20131015/e4bf341e/attachment.htm>

• Previous message: [rabbitmq-discuss] rabbitmq client timeouts, slow responses
• Next message: [rabbitmq-discuss] AlreadyClosedException always sets hardError and initiatedByApplication to true
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]