qpid-proton mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rafael H. Schloming (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (PROTON-255) Messenger stall in send(): frames buffered in transport not written to driver.
Date Thu, 17 Oct 2013 18:10:51 GMT

     [ https://issues.apache.org/jira/browse/PROTON-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rafael H. Schloming resolved PROTON-255.
----------------------------------------

       Resolution: Fixed
    Fix Version/s: 0.5

> Messenger stall in send(): frames buffered in transport not written to driver.
> ------------------------------------------------------------------------------
>
>                 Key: PROTON-255
>                 URL: https://issues.apache.org/jira/browse/PROTON-255
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c
>    Affects Versions: 0.4
>            Reporter: Ken Giusti
>            Priority: Blocker
>             Fix For: 0.5
>
>
> I've created a simple "ping-pong" test between two Messenger clients.  One client sends
10k messages to the other, which replies.  The test stalls after sending 10 messages in each
direction, which is the value used for link credit.
> The cause of the problem is that the FLOW frame sent by one client is not be received
by the other.  The failure is due to the FLOW frame remaining buffered in the sender's transport
buffer, not being written to the driver.  The driver is waiting for socket activity, and never
"sees" the pending output sitting in the transport.
> This bug appears to have been introduced by PROTON-225



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

Mime
View raw message