[
https://issues.apache.org/jira/browse/PROTON-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812951#comment-13812951
]
Ted Ross commented on PROTON-401:
---------------------------------
That works for me. I just don't want to "poll" the drain in case someone might
care.
The way it is now, a broker/intermediary that is idle with no enqueued messages
needs to hammer away at pn_link_drained for each outgoing link.
qpid::messaging::fetch now hangs when receiving from Dispatch because of this.
When can we get a fix?
> Ordering issue prevents credit drain from working properly
> ----------------------------------------------------------
>
> Key: PROTON-401
> URL: https://issues.apache.org/jira/browse/PROTON-401
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
> Affects Versions: 0.5
> Reporter: Ken Giusti
> Assignee: Rafael H. Schloming
> Fix For: 0.6
>
> Attachments: drain-error.patch, drain-hack.patch
>
>
> If the sending link calls pn_link_drained() to indicate that it has send all
> pending data, and afterwards it receives a Flow frame with drain=true from
> the peer, then the drain never completes.
> The ordering is the problem: if the flow frame w/drain=true is received
> _BEFORE_ the sender calls pn_link_drained(), then it works.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
