[PROTON-1914] [c] receiver cannot settle an incomplete incoming message

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: proton-c-0.24.0
• Fix Version/s: proton-c-0.34.0
• Component/s: proton-c
• Assignee: Andrew Stitcher
• Reporter: Alan Conway
• Created: 10/Aug/18 18:54
• Updated: 12/Apr/21 08:35
• Resolved: 14/Dec/20 17:33

Description

AMQP allows a receiver to settle an incoming message before it has all been received, e.g. to reject a large message without receiving it all. However the receiver must still be prepared to receive frames of the message that might have been in flight, until it gets the remote settle.

Proton does not support this. Settling an incomplete incoming message advances the receiver's delivery-id. Subsequent frames cause and error like: "amqp:session:invalid-field:sequencing error, expected delivery-id 1, got 0"

Issue Links

• is duplicated by: PROTON-2050 Attempting to settle a rx multiframe message part way can cause connection drop
• is related to: PROTON-2186 On released callback invoked twice for same delivery tag
• is related to: DISPATCH-1045 Sometimes close connetion after releasing partial multi-frame messsage
• is related to: DISPATCH-1110 Intermittent router hang while running QIT's AMQP large content test
• relates to: PROTON-2056 [proton-python] on_settled callback not called when disposition arrives in 2 frames