[
https://issues.apache.org/jira/browse/PROTON-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058225#comment-15058225
]
ASF subversion and git services commented on PROTON-1077:
---------------------------------------------------------
Commit 3a8782b9871fa35db0c69c994c4c4667251242b0 in qpid-proton's branch
refs/heads/0.11.x from Robert Gemmell
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=3a8782b ]
PROTON-1077: adjust the receivers transport credit state by the same delta as
the link credit state when deliveryCount advances to keep them in sync
(cherry picked from commit a8d87bb3c6d54458d7041d38374feb8b7cf30667)
> receiver link and transport view of credit can become disjoint when sending
> link sends flow frames
> --------------------------------------------------------------------------------------------------
>
> Key: PROTON-1077
> URL: https://issues.apache.org/jira/browse/PROTON-1077
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-j
> Affects Versions: 0.11
> Reporter: Robbie Gemmell
>
> If a recieving link receives flow frames from the sending peer updating
> advancing the delivery count [and setting credit to 0], then recieves flow
> frames from the sender updating credit but not advancing the delivery count,
> then receives messages, the Link and TransportLink views of the credit can
> become disjoint, leading applications to think they have a different amount
> of credit than they actually do, and leading to a different amount of new
> credit being flowed to the sender than expected, even none.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
