You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Andrew Stitcher (JIRA)" <ji...@apache.org> on 2016/07/14 18:29:20 UTC
[jira] [Created] (PROTON-1258) No transport_close event is
generated on the listening side of the connection
Andrew Stitcher created PROTON-1258:
---------------------------------------
Summary: No transport_close event is generated on the listening side of the connection
Key: PROTON-1258
URL: https://issues.apache.org/jira/browse/PROTON-1258
Project: Qpid Proton
Issue Type: Bug
Components: cpp-binding
Affects Versions: 0.13.0
Reporter: Andrew Stitcher
Assignee: Andrew Stitcher
Transport event handling is inconsistent between the listening and connecting sides of an AMQP connection:
On the client the transport events happen as they should - you always get transport_open an optional transport_error and transport_close.
On the server you get the transport_open, but no transport_close. However if the connection is interrupted for some reason (say the socket disconnects) then you will transport_error, followed by transport_close.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org