Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
M3
-
None
Description
When a command is waiting for its result on a future it is notified of a connection closed event through a RuntimeException. This is an issue especially when the connection is closed by the broker because the command was erroneous. The connectionClosed event with the corresponding error code is currently dispatched to the connection exception listener.
one solution would be for the connection delegate of org.apache.qpidity.nclient.Client to notify its org.apache.qpidity.nclient.Session that the connection has been closed by the broker. The sessions would then close all its pending commands with the corresponding error code/exception.