[PROTON-1077] receiver link and transport view of credit can become disjoint when sending link sends flow frames

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: proton-0.11.0
• Fix Version/s: proton-0.11.1, proton-0.12.0
• Component/s: proton-j
• Assignee: Robbie Gemmell
• Reporter: Robbie Gemmell
• Created: 14/Dec/15 12:13
• Updated: 07/Jan/16 12:17
• Resolved: 18/Dec/15 15:18

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.

Issue Links

• is depended upon by: QPIDJMS-139 Message flow to synchronous consumer from Qpid Java broker unexpectedly ceases
• is related to: QPID-6947 [Java Broker] deliverycount advanced outside a previous drain attempt that used all credit
• is related to: QPID-6863 AMQP 1.0 message flow to consumers stops