You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Ted Ross (JIRA)" <ji...@apache.org> on 2016/05/10 17:58:12 UTC

[jira] [Resolved] (DISPATCH-53) waypoints are not robust if targets not set up in advance.

     [ https://issues.apache.org/jira/browse/DISPATCH-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ted Ross resolved DISPATCH-53.
------------------------------
       Resolution: Fixed
         Assignee: Ted Ross
    Fix Version/s: 0.6.0

> waypoints are not robust if targets not set up in advance.
> ----------------------------------------------------------
>
>                 Key: DISPATCH-53
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-53
>             Project: Qpid Dispatch
>          Issue Type: Bug
>          Components: Router Node
>            Reporter: Alan Conway
>            Assignee: Ted Ross
>            Priority: Minor
>             Fix For: 0.6.0
>
>
> When using a waypoint to route via an external broker queue (see tests/system_tests_broker.py), you need to:
> 1. start the broker and create the queue _before_ starting the router.
> 2. wait for the router to establish a connection to the broker _before_ sending messages.
> We also need to consider the behavior if a waypoint is invalidated after it has been in use, either by the connection dropping or the broker queue being deleted.
> We could hold messages up to some time/space limit in the hope that the waypoint will be (re-)activated, or we can just drop them. It would be good to be able to notify the sender but currently we don't have a way to do so.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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