[
https://issues.apache.org/jira/browse/DISPATCH-1337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849906#comment-16849906
]
ASF subversion and git services commented on DISPATCH-1337:
-----------------------------------------------------------
Commit 9c2e0b4f4564a5cbcd7bf97af62f0078c7e1f04e in qpid-dispatch's branch
refs/heads/master from Ted Ross
[ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=9c2e0b4 ]
DISPATCH-1337 - Added fallback-link feature
This closes #507
> Fallback Destination for Unreachable Addresses
> ----------------------------------------------
>
> Key: DISPATCH-1337
> URL: https://issues.apache.org/jira/browse/DISPATCH-1337
> Project: Qpid Dispatch
> Issue Type: New Feature
> Components: Router Node
> Reporter: Ted Ross
> Assignee: Ted Ross
> Priority: Major
> Fix For: 1.8.0
>
>
> This feature allows addresses to be configured such that an alternate
> fallback destination can be used to receive messages that are not deliverable
> to any normal consumers on the address.
> Typically, this feature will be used to allow a message broker to store
> messages that are not routable directly to consumers. When one or more
> consumers are attached in the router network, messages shall be delivered
> directly to the consumers. Where there are no reachable consumers,
> deliveries shall then be diverted to any fallback links that are attached.
> Once consumers re-connect to the network, messages shall again be delivered
> directly.
> When a consumer comes online after messages have been stored in a broker, it
> shall receive the stored messages interleaved with new messages from
> producers. No attempt shall be made by the router network to preserve the
> original delivery order of the messages.
> This feature can be configured by adding the attribute
> {noformat}
> enableFallback: yes
> {noformat}
> to an address configuration. This attribute tells the router that any address
> matching the configuration shall support the fallback destination capability.
> There are two ways to create a fallback link for an address:
> Using auto-links:
> An auto-link (or a pair of auto-links) can be configured to create a fallback
> link for an address. For example, assume that there is a route-container
> connector or listener for a broker called "alternate-broker".
> {noformat}
> address {
> prefix: position_update
> enableFallback: yes
> }
> autoLink {
> address: position_update.338
> direction: in
> connection: alternate-broker
> fallback: yes
> }
> autoLink {
> address: position_update.338
> direction: out
> connection: alternate-broker
> fallback: yes
> }
> {noformat}
> The above configuration will use a queue on the broker called
> "position_update.338" as the fallback destination for direct consumers.
> Furthermore, since there are both _in_ and _out_ auto-links, the router(s)
> shall send queued messages to newly attached direct consumers.
> Using terminus capabilities:
> As an alternative to using auto-links, the broker (or any other process) can
> attach sending and receiving links to the address with terminus-capability
> "qd.fallback". This will create the same behavior as the above example.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
