[rabbitmq-discuss] AlreadyClosedException always sets hardError and initiatedByApplication to true
mklishin at gopivotal.com
Tue Oct 15 23:45:32 BST 2013
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?
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?
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 495 bytes
Desc: Message signed with OpenPGP using GPGMail
More information about the rabbitmq-discuss