qpid-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From gmur...@apache.org
Subject qpid-dispatch git commit: DISPATCH-1064 - Doc link route and autolink connection failure behavior. This closes #339
Date Mon, 06 Aug 2018 15:13:18 GMT
Repository: qpid-dispatch
Updated Branches:
  refs/heads/master 69c093f93 -> 6cc87192a


DISPATCH-1064 - Doc link route and autolink connection failure behavior. This closes #339


Project: http://git-wip-us.apache.org/repos/asf/qpid-dispatch/repo
Commit: http://git-wip-us.apache.org/repos/asf/qpid-dispatch/commit/6cc87192
Tree: http://git-wip-us.apache.org/repos/asf/qpid-dispatch/tree/6cc87192
Diff: http://git-wip-us.apache.org/repos/asf/qpid-dispatch/diff/6cc87192

Branch: refs/heads/master
Commit: 6cc87192a98722e6380aa4708f36692e791ec27d
Parents: 69c093f
Author: Ben Hardesty <bhardest@redhat.com>
Authored: Mon Jul 9 16:44:49 2018 -0400
Committer: Ganesh Murthy <gmurthy@redhat.com>
Committed: Mon Aug 6 11:13:02 2018 -0400

----------------------------------------------------------------------
 docs/books/user-guide/routing.adoc | 12 ++++++++++++
 1 file changed, 12 insertions(+)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/qpid-dispatch/blob/6cc87192/docs/books/user-guide/routing.adoc
----------------------------------------------------------------------
diff --git a/docs/books/user-guide/routing.adoc b/docs/books/user-guide/routing.adoc
index 92dea24..b9225ff 100644
--- a/docs/books/user-guide/routing.adoc
+++ b/docs/books/user-guide/routing.adoc
@@ -325,6 +325,11 @@ After you add waypoint addresses to identify the broker queue, you must
connect
 
 With autolinks, client traffic is handled on the router, not the broker. Clients attach their
links to the router, and then the router uses internal autolinks to connect to the queue on
the broker. Therefore, the queue will always have a single producer and a single consumer
regardless of how many clients are attached to the router.
 
+[NOTE]
+====
+If the connection to the broker fails, {RouterName} automatically attempts to reestablish
the connection and reroute message deliveries to any available alternate destinations. However,
some deliveries could be returned to the sender with a `RELEASED` or `MODIFIED` disposition.
Therefore, you should ensure that your clients can handle these deliveries appropriately (generally
by resending them).
+====
+
 . If this router is different than the router that is connected to the clients, then add
the waypoint address.
 
 . Add an outgoing connection to the broker:
@@ -551,6 +556,13 @@ Link routes establish a link between a sender and a receiver that travels
throug
 
 With link routing, client traffic is handled on the broker, not the router. Clients have
a direct link through the router to a broker's queue. Therefore, each client is a separate
producer or consumer.
 
+[NOTE]
+====
+If the connection to the broker fails, the routed links are detached, and the router will
attempt to reconnect to the broker (or its backup). Once the connection is reestablished,
the link route to the broker will become reachable again.
+
+From the client's perspective, the client will see the detached links (that is, the senders
or receivers), but not the failed connection. Therefore, if you want the client to reattach
dropped links in the event of a broker connection failure, you must configure this functionality
on the client. Alternatively, you can use message routing with autolinks instead of link routing.
For more information, see xref:routing-messages-through-broker[Routing Messages through a
Broker Queue].
+====
+
 .Procedure
 
 . In the router configuration file, add an outgoing connection to the broker:


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


Mime
View raw message