ASF GitHub Bot commented on DISPATCH-1064:

Github user ted-ross commented on a diff in the pull request:

    --- Diff: docs/books/user-guide/routing.adoc ---
    @@ -102,6 +102,17 @@ Link routing supports local transactions to a broker.
     With a link route, consumers can provide server-side selectors for broker 
    +=== Considerations for Broker Connection Failure Handling
    +The message routing and link routing mechanisms both enable you to 
transfer messages to brokers. However, they differ in how they behave if the 
connection to the broker is lost. If you require the ability for the connection 
to be reestablished automatically, you should use message routing (with 
    +With link routing::
    +The client appears to be directly connected to the broker even though it 
is actually connected to a router, which is link routed to the broker. If the 
broker goes offline, the router sees the connection failure and closes all of 
the routed links that were attached to the broker. The client's connection to 
the router, however, remains open. Therefore, the client does not see the 
connection failure between the broker and the router and does not attempt to 
reestablish it.
    +With message routing using autolinks::
    +The client is connected to a router, and the router is connected to the 
broker. Therefore, if the broker goes offline, the router will see the 
connection failure and attempt to reestablish the connection when the broker 
comes back online.
    --- End diff --
    In the case of message routing, the router network will automatically 
reroute deliveries to alternate destinations if they are available.  There will 
likely be some deliveries that are returned to the sender with RELEASED 
disposition meaning that they were not delivered anywhere.  Deliveries may also 
come back with MODIFIED/undeliverable disposition indicating that they _may_ 
have been delivered, but were not settled.
    If there is only one broker in a message-routing/autolink deployment and 
that broker goes offline, senders to the broker will see their deliveries 
RELEASED and eventually will experience backpressure (no new credit) until the 
broker comes back online.

> Doc link route reconnect behavior
> ---------------------------------
>                 Key: DISPATCH-1064
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-1064
>             Project: Qpid Dispatch
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 1.2.0
>            Reporter: Ben Hardesty
>            Assignee: Ben Hardesty
>            Priority: Major
> When the router is configured with a linkRoute and client connects using 
> failover, the link will not be reestablished should the router's connection 
> to the broker fail. If auto-reconnect isĀ  required, the router should be 
> configured with autoLink.

This message was sent by Atlassian JIRA

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

Reply via email to