[
https://issues.apache.org/jira/browse/PROTON-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17079422#comment-17079422
]
Jiri Daněk commented on PROTON-2186:
------------------------------------
[~fgiorget] Do you mean this workaround?
https://github.com/rh-messaging-qe/iqa_testsuite/blob/4915aff73d9acc50eb2cc9049d0b1d75612c29dd/integration/int_3Ri_2BhaRi2_3Re_2BhaRe3/sender.py#L164-L171
{code:python}
def on_released(self, event):
# from qpid_dispatch system tests:
# for some reason Proton 'helpfully' calls on_released even though the
# delivery state is actually MODIFIED
if event.delivery.remote_state == Delivery.MODIFIED:
return self.on_modified(event)
self.released += 1
logging.debug('Message released - %s' % event.delivery.tag)
{code}
> On released callback invoked twice for same delivery tag
> --------------------------------------------------------
>
> Key: PROTON-2186
> URL: https://issues.apache.org/jira/browse/PROTON-2186
> Project: Qpid Proton
> Issue Type: Bug
> Components: python-binding
> Reporter: Fernando Giorgetti
> Priority: Major
>
> 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]
