[PROTON-1902] arriving aborted transfers are mishandled and can't be observed

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: proton-j-0.27.2, proton-j-0.28.0
• Fix Version/s: proton-j-0.27.3, proton-j-0.28.1
• Component/s: proton-j
• Assignee: Robbie Gemmell
• Reporter: Robbie Gemmell
• Created: 30/Jul/18 12:43
• Updated: 17/May/21 22:05
• Resolved: 30/Jul/18 12:50

Description

When an arriving delivery is aborted by its final transfer frame, the transport session mishandles it. The 'aborted' flag is not considered properly and fails to override the flags for 'more' and 'settled' (aborted deliveries are implicitly settled), the transfer frames payload if any is not discarded as required, and the delivery count and credit aren't updated, so any future flow frames sent will fail to account for it properly. No attempt is made to track that the abort happened, so there is also no way for the using application code to detect that the delivery was aborted and will remain 'partial' indefinitely.

Issue Links

• fixes: PROTON-1581 Expose the "aborted" flag for transferred deliveries