[PROTON-2050] Attempting to settle a rx multiframe message part way can cause connection drop

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: proton-c-0.27.1, proton-c-0.28.0
• Component/s: proton-c, python-binding
• Assignee: Unassigned
• Reporter: Ken Giusti
• Created: 15/May/19 19:49
• Updated: 16/May/19 13:54
• Resolved: 16/May/19 13:54

Description

Unsure if expected behavior:

If a receiver settles an inbound message before all frames have arrived, any buffered frames (including frames buffered in the sender) that arrive after the settlement causes the connection to close. See the following router log:

2019-05-15 15:38:47.133438 -0400 SERVER (trace) [86]:0 -> @transfer(20) [handle=0, delivery-id=1, delivery-tag=b"\x1f\x07\x00\x00\x00\x00\x00\x00", message-format=0, more=true] (32768) "ZZZ"... (truncated) (/home/kgiusti/tmp/qpid-dispatch/src/server.c:106)

2019-05-15 15:38:47.135611 0400 SERVER (trace) [86]:0 < @disposition(21) [role=true, first=1, settled=true, state=@released(38) []] (/home/kgiusti/tmp/qpid-dispatch/src/server.c:106)

2019-05-15 15:38:47.135732 0400 SERVER (trace) [86]:0 < @close(24) [error=@error(29) [condition=:"amqp:session:invalid-field", description="sequencing error, expected delivery-id 2, got 1"]] (/home/kgiusti/tmp/qpid-dispatch/src/server.c:106)

2019-05-15 15:38:47.135780 0400 SERVER (trace) [86]: < EOS (/home/kgiusti/tmp/qpid-dispatch/src/server.c:106)

A reproducer has been added to the router unit tests (early close) via the following patch:

dispatch test patch

Issue Links

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