[
https://issues.apache.org/jira/browse/DISPATCH-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17091760#comment-17091760
]
ASF subversion and git services commented on DISPATCH-1626:
-----------------------------------------------------------
Commit 6fc8dd138c7b85fc029877d84cc257ebdb45c034 in qpid-dispatch's branch
refs/heads/master from Ganesh Murthy
[ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=6fc8dd1 ]
DISPATCH-1626 - Modified AMQP_rx_handler to call pn_delivery_update() only for
aborted deliveries. This ensures that only one dispostion is sent for a
pn_delivery. This closes #725
> On released callback invoked twice for same delivery tag
> --------------------------------------------------------
>
> Key: DISPATCH-1626
> URL: https://issues.apache.org/jira/browse/DISPATCH-1626
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Container
> Affects Versions: 1.11.0
> Reporter: Ganesh Murthy
> Assignee: Ganesh Murthy
> Priority: Major
> Fix For: 1.12.0
>
> Attachments: qdrouterd.conf, simple_recv_release.py,
> simple_send_large.py
>
>
> 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:
> {noformat}
> [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) []]{noformat}
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
