[
https://issues.apache.org/jira/browse/DISPATCH-523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15535844#comment-15535844
]
ASF subversion and git services commented on DISPATCH-523:
----------------------------------------------------------
Commit 74cee2f39a218bd93a59befbd135ca7c5581cd61 in qpid-dispatch's branch
refs/heads/0.6.x from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=74cee2f ]
DISPATCH-523 - Make sure deliveries that _should_ be deliverable but are not
get released.
> Topology changes can cause in-flight deliveries to be stuck in the ingress
> router
> ---------------------------------------------------------------------------------
>
> Key: DISPATCH-523
> URL: https://issues.apache.org/jira/browse/DISPATCH-523
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Router Node
> Affects Versions: 0.6.1
> Reporter: Ted Ross
> Assignee: Ted Ross
> Priority: Blocker
> Fix For: 0.7.0, 0.6.2
>
>
> Scenario:
> - A network where messages are being delivered from the ingress router,
> across a neighbor router to a third router where the destination is attached.
> - The neighbor router is shut down.
> - There is a valid alternative path to the destination.
> - A message delivery arrives immediately after the neighbor router is lost
> (before the route engine can compute the new path).
> In the above scenario, the delivery may wind up on the ingress link's
> "undelivered" list and stay there indefinitely, even after the network has
> been completely restored.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
