[ https://issues.apache.org/jira/browse/DISPATCH-523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ted Ross resolved DISPATCH-523. ------------------------------- Resolution: Fixed > 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 > > > 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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org