You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/11/26 16:54:39 UTC

[jira] [Commented] (PROTON-466) Driver - Optimization causes hangs in cleanly closed connections

    [ https://issues.apache.org/jira/browse/PROTON-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13832705#comment-13832705 ] 

ASF subversion and git services commented on PROTON-466:
--------------------------------------------------------

Commit 1545697 from [~tedross] in branch 'proton/trunk'
[ https://svn.apache.org/r1545697 ]

PROTON-466 - driver fix.

> Driver - Optimization causes hangs in cleanly closed connections
> ----------------------------------------------------------------
>
>                 Key: PROTON-466
>                 URL: https://issues.apache.org/jira/browse/PROTON-466
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c
>    Affects Versions: 0.5
>            Reporter: Ted Ross
>            Assignee: Ted Ross
>            Priority: Blocker
>             Fix For: 0.6
>
>         Attachments: PROTON-446.patch
>
>
> Related to https://issues.apache.org/jira/browse/QPID-4853
> Often, when a connection is cleanly closed, the connection-close handshake completes but the connector is never closed.  All that is needed is for one more connector_process cycle, but the connector never again appears in the work list.
> There is an optimization in the connector processor that says "if the socket has accepted all of the current data for send, clear the SEL_WR flag".  The problem is that when the data-for-send is the last data to be sent on the connection, the connector is never again processed and hangs, using resources and keeping the socket from fully closing.



--
This message was sent by Atlassian JIRA
(v6.1#6144)