You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/10/18 14:44:00 UTC
[jira] [Commented] (DISPATCH-829) The router does not set the
"aborted" indication on truncated, streamed deliveries
[ https://issues.apache.org/jira/browse/DISPATCH-829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16209455#comment-16209455 ]
ASF subversion and git services commented on DISPATCH-829:
----------------------------------------------------------
Commit 9871fdbfccb749c410a9f5d2ed9784e542026233 in qpid-dispatch's branch refs/heads/master from [~tross@redhat.com]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=9871fdb ]
DISPATCH-829 - Added labels and debug logs to diagnose delivery ref-count issues.
> The router does not set the "aborted" indication on truncated, streamed deliveries
> ----------------------------------------------------------------------------------
>
> Key: DISPATCH-829
> URL: https://issues.apache.org/jira/browse/DISPATCH-829
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Router Node
> Affects Versions: 1.0.0
> Reporter: Ted Ross
> Assignee: Chuck Rolke
> Fix For: 1.0.0
>
>
> Dispatch Router neither honors nor sets the aborted flag in deliveries. Now that Proton supports this flag and Dispatch Router supports large-message streaming, this is a bug that needs to be fixed.
> There are two primary cases:
> # A streaming delivery is passing through the router when the sender's connection/session/link drops mid-delivery. The router _must_ set the aborted flag on the outbound delivery so that the receiving container will know that the delivery is no good.
> # A delivery arrives on the router with the aborted flag set. It _must_ either drop the delivery (if it has not yet been forwarded) or propagate the aborted flag (if earlier frames of the delivery have already been forwarded).
> Please note that in a multi-router network, both of the above cases can occur on the same message. If the sender drops before completing the delivery, the ingress router must handle case 1. Downstream routers handling the delivery will experience case 2.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org