[
https://issues.apache.org/jira/browse/PROTON-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17079357#comment-17079357
]
Jiri Daněk edited comment on PROTON-2186 at 4/9/20, 1:46 PM:
-------------------------------------------------------------
[~fgiorget] These are frames logged from Qpid Dispatch? That is, these two are
frames that Qpid Dispatch is sending to the client? Why is it sending two
dispositions? What do you think the client is supposed to do, in response to
the first disposition, and in response to the second disposition.
How often is this happening? Is there some special procedure to trigger the
issue, or does it happen at random during normal message traffic? Do I need to
stress the router network somehow for this to happen? Can I reproduce with a
single router or do I need a router network?
Does this issue come from some automated test suite that I could rerun, or is
it from production?
was (Author: jdanek):
[~fgiorget] These are frames logged from Qpid Dispatch? That is, these are two
are frames that Qpid Dispatch is sending to the client? Why is it sending two
dispositions? What do you think the client is supposed to do, in response to
the first disposition, and in response to the second disposition.
How often is this happening? Is there some special procedure to trigger the
issue, or does it happen at random during normal message traffic? Do I need to
stress the router network somehow for this to happen? Can I reproduce with a
single router or do I need a router network?
Does this issue come from some automated test suite that I could rerun, or is
it from production?
> 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
> 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]
