[
https://issues.apache.org/jira/browse/DISPATCH-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17090796#comment-17090796
]
ASF GitHub Bot commented on DISPATCH-1626:
------------------------------------------
ganeshmurthy opened a new pull request #725:
URL: https://github.com/apache/qpid-dispatch/pull/725
… only for aborted deliveries. This ensures that only one dispostion is sent
for a pn_delivery"
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> 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]
