Client times out connections rather than picking up close exception
-------------------------------------------------------------------
Key: QPID-1715
URL: https://issues.apache.org/jira/browse/QPID-1715
Project: Qpid
Issue Type: Bug
Components: Java Client
Affects Versions: M4, M3, M2.1, M2, M5
Reporter: Martin Ritchie
Currently, when the the broker sends a ConnectionClose, due to an error or
client behaviour. The client correctly response OK and then proceeds to shut
the socket.
However, it fails to remember that it has done this. Whilst the associated
error is propagated the client then is no longer blocked and often, at least
in our tests, then closes the connection.
Problem is the ConnectionClose Handling thread has often already started that,
as a result the main application thread hangs for the time out period as the
socket is closed and there is nothing to notify it that the write will never
succeed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
