[PROTON-2186] On released callback invoked twice for same delivery tag

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: proton-c-0.29.0
• Component/s: python-binding
• Assignee: Unassigned
• Reporter: Fernando Giorgetti
• Created: 25/Mar/20 19:39
• Updated: 23/Apr/20 17:28
• Resolved: 22/Apr/20 14:36

Description

In a python client application, that is connected to a dispatch router, I have observed that the on_released callback was invoked twice for the same delivery tag.

Here are the disposition frames I was able to capture for the respective delivery:

[0x562a0083ed80]:0 <- @disposition(21) [role=true, first=981, state=@released(38) []]
[0x562a0083ed80]:0 <- @disposition(21) [role=true, first=981, last=982, settled=true, state=@released(38) []]

The delivery tag 981 came first without the settlement and next with the settled as true. And the on_released was called twice for the 981 delivery tag.

 

Issue Links

• is superceded by: DISPATCH-1626 On released callback invoked twice for same delivery tag
• relates to: PROTON-1914 [c] receiver cannot settle an incomplete incoming message
• relates to: PROTON-2056 [proton-python] on_settled callback not called when disposition arrives in 2 frames