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

Robbie Gemmell updated PROTON-1077:
-----------------------------------
    Description: 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.  (was: If a 
recieving link receives flow frames from the sending peer updating credit but 
not advancing the delivery count, 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.)

> 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)

Reply via email to