You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/07/14 19:43:20 UTC
[jira] [Commented] (PROTON-1258) No transport_close event is
generated on the listening side of the connection
[ https://issues.apache.org/jira/browse/PROTON-1258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15378222#comment-15378222 ]
ASF subversion and git services commented on PROTON-1258:
---------------------------------------------------------
Commit 4a6010110296846e3c77defc0558a45d8792d3b5 in qpid-proton's branch refs/heads/master from [~astitcher]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=4a60101 ]
PROTON-1258: Make transport events more consistent on client and server
> 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