qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DISPATCH-829) The router does not set the "aborted" indication on truncated, streamed deliveries
Date Wed, 18 Oct 2017 14:44:01 GMT

    [ https://issues.apache.org/jira/browse/DISPATCH-829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16209458#comment-16209458

ASF subversion and git services commented on DISPATCH-829:

Commit fea60bc83210ab5ae714f346b4209f27fc807139 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=fea60bc ]

DISPATCH-829 - Added a multicast-truncated test

> 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

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message