[rabbitmq-discuss] AlreadyClosedException always sets hardError and initiatedByApplication to true
jhalterman at gmail.com
Tue Oct 15 22:24:58 BST 2013
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?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss