Added: websites/production/activemq/content/artemis/docs/1.5.4/core-bridges.html
==============================================================================
--- websites/production/activemq/content/artemis/docs/1.5.4/core-bridges.html
(added)
+++ websites/production/activemq/content/artemis/docs/1.5.4/core-bridges.html
Sun Mar 12 16:08:18 2017
@@ -0,0 +1,1199 @@
+
+<!DOCTYPE HTML>
+<html lang="" >
+ <head>
+ <title>Core Bridges · ActiveMQ Artemis Documentation</title>
+ <meta charset="UTF-8">
+ <meta http-equiv="X-UA-Compatible" content="IE=edge" />
+ <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
+ <meta name="description" content="">
+ <meta name="generator" content="GitBook 3.1.1">
+
+
+
+
+ <link rel="stylesheet" href="gitbook/style.css">
+
+
+
+
+ <link rel="stylesheet"
href="gitbook/gitbook-plugin-highlight/website.css">
+
+
+
+ <link rel="stylesheet"
href="gitbook/gitbook-plugin-search/search.css">
+
+
+
+ <link rel="stylesheet"
href="gitbook/gitbook-plugin-fontsettings/website.css">
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ <meta name="HandheldFriendly" content="true"/>
+ <meta name="viewport" content="width=device-width, initial-scale=1,
user-scalable=no">
+ <meta name="apple-mobile-web-app-capable" content="yes">
+ <meta name="apple-mobile-web-app-status-bar-style" content="black">
+ <link rel="apple-touch-icon-precomposed" sizes="152x152"
href="gitbook/images/apple-touch-icon-precomposed-152.png">
+ <link rel="shortcut icon" href="gitbook/images/favicon.ico"
type="image/x-icon">
+
+
+ <link rel="next" href="duplicate-detection.html" />
+
+
+ <link rel="prev" href="diverts.html" />
+
+
+ </head>
+ <body>
+
+<div class="book">
+ <div class="book-summary">
+
+
+<div id="book-search-input" role="search">
+ <input type="text" placeholder="Type to search" />
+</div>
+
+
+ <nav role="navigation">
+
+
+
+<ul class="summary">
+
+
+
+
+
+
+
+
+
+ <li class="chapter " data-level="1.1" data-path="./">
+
+ <a href="./">
+
+
+ Introduction
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.2" data-path="notice.html">
+
+ <a href="notice.html">
+
+
+ Legal Notice
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.3" data-path="preface.html">
+
+ <a href="preface.html">
+
+
+ Preface
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.4" data-path="project-info.html">
+
+ <a href="project-info.html">
+
+
+ Project Info
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.5"
data-path="messaging-concepts.html">
+
+ <a href="messaging-concepts.html">
+
+
+ Messaging Concepts
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.6" data-path="architecture.html">
+
+ <a href="architecture.html">
+
+
+ Architecture
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.7" data-path="using-server.html">
+
+ <a href="using-server.html">
+
+
+ Using the Server
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.8" data-path="using-jms.html">
+
+ <a href="using-jms.html">
+
+
+ Using JMS
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.9" data-path="using-core.html">
+
+ <a href="using-core.html">
+
+
+ Using Core
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.10"
data-path="jms-core-mapping.html">
+
+ <a href="jms-core-mapping.html">
+
+
+ Mapping JMS Concepts to the Core API
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.11"
data-path="client-classpath.html">
+
+ <a href="client-classpath.html">
+
+
+ The Client Classpath
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.12" data-path="examples.html">
+
+ <a href="examples.html">
+
+
+ Examples
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.13"
data-path="wildcard-routing.html">
+
+ <a href="wildcard-routing.html">
+
+
+ Routing Messages With Wild Cards
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.14"
data-path="wildcard-syntax.html">
+
+ <a href="wildcard-syntax.html">
+
+
+ Understanding the Apache ActiveMQ Artemis Wildcard Syntax
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.15"
data-path="filter-expressions.html">
+
+ <a href="filter-expressions.html">
+
+
+ Filter Expressions
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.16" data-path="persistence.html">
+
+ <a href="persistence.html">
+
+
+ Persistence
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.17"
data-path="configuring-transports.html">
+
+ <a href="configuring-transports.html">
+
+
+ Configuring Transports
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.18" data-path="config-reload.html">
+
+ <a href="config-reload.html">
+
+
+ Configuration Reload
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.19" data-path="connection-ttl.html">
+
+ <a href="connection-ttl.html">
+
+
+ Detecting Dead Connections
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.20" data-path="slow-consumers.html">
+
+ <a href="slow-consumers.html">
+
+
+ Detecting Slow Consumers
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.21"
data-path="transaction-config.html">
+
+ <a href="transaction-config.html">
+
+
+ Resource Manager Configuration
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.22" data-path="flow-control.html">
+
+ <a href="flow-control.html">
+
+
+ Flow Control
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.23"
data-path="send-guarantees.html">
+
+ <a href="send-guarantees.html">
+
+
+ Guarantees of sends and commits
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.24"
data-path="undelivered-messages.html">
+
+ <a href="undelivered-messages.html">
+
+
+ Message Redelivery and Undelivered Messages
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.25" data-path="message-expiry.html">
+
+ <a href="message-expiry.html">
+
+
+ Message Expiry
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.26" data-path="large-messages.html">
+
+ <a href="large-messages.html">
+
+
+ Large Messages
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.27" data-path="paging.html">
+
+ <a href="paging.html">
+
+
+ Paging
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.28"
data-path="queue-attributes.html">
+
+ <a href="queue-attributes.html">
+
+
+ Queue Attributes
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.29"
data-path="scheduled-messages.html">
+
+ <a href="scheduled-messages.html">
+
+
+ Scheduled Messages
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.30"
data-path="last-value-queues.html">
+
+ <a href="last-value-queues.html">
+
+
+ Last-Value Queues
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.31"
data-path="message-grouping.html">
+
+ <a href="message-grouping.html">
+
+
+ Message Grouping
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.32"
data-path="pre-acknowledge.html">
+
+ <a href="pre-acknowledge.html">
+
+
+ Extra Acknowledge Modes
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.33" data-path="management.html">
+
+ <a href="management.html">
+
+
+ Management
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.34" data-path="security.html">
+
+ <a href="security.html">
+
+
+ Security
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.35"
data-path="resource-limits.html">
+
+ <a href="resource-limits.html">
+
+
+ Resource Limits
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.36" data-path="jms-bridge.html">
+
+ <a href="jms-bridge.html">
+
+
+ The JMS Bridge
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.37"
data-path="client-reconnection.html">
+
+ <a href="client-reconnection.html">
+
+
+ Client Reconnection and Session Reattachment
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.38" data-path="diverts.html">
+
+ <a href="diverts.html">
+
+
+ Diverting and Splitting Message Flows
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter active" data-level="1.39"
data-path="core-bridges.html">
+
+ <a href="core-bridges.html">
+
+
+ Core Bridges
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.40"
data-path="duplicate-detection.html">
+
+ <a href="duplicate-detection.html">
+
+
+ Duplicate Message Detection
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.41" data-path="clusters.html">
+
+ <a href="clusters.html">
+
+
+ Clusters
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.42" data-path="ha.html">
+
+ <a href="ha.html">
+
+
+ High Availability and Failover
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.43"
data-path="graceful-shutdown.html">
+
+ <a href="graceful-shutdown.html">
+
+
+ Graceful Server Shutdown
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.44" data-path="libaio.html">
+
+ <a href="libaio.html">
+
+
+ Libaio Native Libraries
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.45" data-path="thread-pooling.html">
+
+ <a href="thread-pooling.html">
+
+
+ Thread management
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.46" data-path="logging.html">
+
+ <a href="logging.html">
+
+
+ Logging
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.47" data-path="rest.html">
+
+ <a href="rest.html">
+
+
+ REST Interface
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.48"
data-path="embedding-activemq.html">
+
+ <a href="embedding-activemq.html">
+
+
+ Embedding Apache ActiveMQ Artemis
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.49" data-path="karaf.html">
+
+ <a href="karaf.html">
+
+
+ Apache Karaf
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.50"
data-path="spring-integration.html">
+
+ <a href="spring-integration.html">
+
+
+ Spring Integration
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.51"
data-path="aerogear-integration.html">
+
+ <a href="aerogear-integration.html">
+
+
+ AeroGear Integration
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.52"
data-path="vertx-integration.html">
+
+ <a href="vertx-integration.html">
+
+
+ VertX Integration
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.53"
data-path="cdi-integration.html">
+
+ <a href="cdi-integration.html">
+
+
+ CDI Integration
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.54"
data-path="intercepting-operations.html">
+
+ <a href="intercepting-operations.html">
+
+
+ Intercepting Operations
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.55"
data-path="protocols-interoperability.html">
+
+ <a href="protocols-interoperability.html">
+
+
+ Protocols and Interoperability
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.56" data-path="tools.html">
+
+ <a href="tools.html">
+
+
+ Tools
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.57" data-path="maven-plugin.html">
+
+ <a href="maven-plugin.html">
+
+
+ Maven Plugin
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.58" data-path="unit-testing.html">
+
+ <a href="unit-testing.html">
+
+
+ Unit Testing
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.59" data-path="perf-tuning.html">
+
+ <a href="perf-tuning.html">
+
+
+ Troubleshooting and Performance Tuning
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.60"
data-path="configuration-index.html">
+
+ <a href="configuration-index.html">
+
+
+ Configuration Reference
+
+ </a>
+
+
+
+ </li>
+
+
+
+
+ <li class="divider"></li>
+
+ <li>
+ <a href="https://www.gitbook.com"; target="blank" class="gitbook-link">
+ Published with GitBook
+ </a>
+ </li>
+</ul>
+
+
+ </nav>
+
+
+ </div>
+
+ <div class="book-body">
+
+ <div class="body-inner">
+
+
+
+<div class="book-header" role="navigation">
+
+
+ <!-- Title -->
+ <h1>
+ <i class="fa fa-circle-o-notch fa-spin"></i>
+ <a href="." >Core Bridges</a>
+ </h1>
+</div>
+
+
+
+
+ <div class="page-wrapper" tabindex="-1" role="main">
+ <div class="page-inner">
+
+<div id="book-search-results">
+ <div class="search-noresults">
+
+ <section class="normal markdown-section">
+
+ <h1 id="core-bridges">Core Bridges</h1>
+<p>The function of a bridge is to consume messages from a source queue, and
+forward them to a target address, typically on a different Apache ActiveMQ
Artemis
+server.</p>
+<p>The source and target servers do not have to be in the same cluster
+which makes bridging suitable for reliably sending messages from one
+cluster to another, for instance across a WAN, or internet and where the
+connection may be unreliable.</p>
+<p>The bridge has built in resilience to failure so if the target server
+connection is lost, e.g. due to network failure, the bridge will retry
+connecting to the target until it comes back online. When it comes back
+online it will resume operation as normal.</p>
+<p>In summary, bridges are a way to reliably connect two separate Apache
ActiveMQ Artemis
+servers together. With a core bridge both source and target servers must
+be Apache ActiveMQ Artemis servers.</p>
+<p>Bridges can be configured to provide <em>once and only once</em> delivery
+guarantees even in the event of the failure of the source or the target
+server. They do this by using duplicate detection (described in <a
href="duplicate-detection.html">Duplicate Detection</a>).</p>
+<blockquote>
+<p><strong>Note</strong></p>
+<p>Although they have similar function, don't confuse core bridges with
+JMS bridges!</p>
+<p>Core bridges are for linking an Apache ActiveMQ Artemis node with another
Apache ActiveMQ Artemis
+node and do not use the JMS API. A JMS Bridge is used for linking any
+two JMS 1.1 compliant JMS providers. So, a JMS Bridge could be used
+for bridging to or from different JMS compliant messaging system. It's
+always preferable to use a core bridge if you can. Core bridges use
+duplicate detection to provide <em>once and only once</em> guarantees. To
+provide the same guarantee using a JMS bridge you would have to use XA
+which has a higher overhead and is more complex to configure.</p>
+</blockquote>
+<h2 id="configuring-bridges">Configuring Bridges</h2>
+<p>Bridges are configured in <code>broker.xml</code>. Let's kick off
+with an example (this is actually from the bridge example):</p>
+<pre><code><bridge name="my-bridge">
+ <queue-name>jms.queue.sausage-factory</queue-name>
+
<forwarding-address>jms.queue.mincing-machine</forwarding-address>
+ <filter string="name='aardvark'"/>
+ <transformer-class-name>
+ org.apache.activemq.artemis.jms.example.HatColourChangeTransformer
+ </transformer-class-name>
+ <retry-interval>1000</retry-interval>
+ <ha>true</ha>
+ <retry-interval-multiplier>1.0</retry-interval-multiplier>
+ <initial-connect-attempts>-1</initial-connect-attempts>
+ <reconnect-attempts>-1</reconnect-attempts>
+ <failover-on-server-shutdown>false</failover-on-server-shutdown>
+ <use-duplicate-detection>true</use-duplicate-detection>
+ <confirmation-window-size>10000000</confirmation-window-size>
+ <user>foouser</user>
+ <password>foopassword</password>
+ <static-connectors>
+ <connector-ref>remote-connector</connector-ref>
+ </static-connectors>
+ <!-- alternative to static-connectors
+ <discovery-group-ref
discovery-group-name="bridge-discovery-group"/>
+ -->
+</bridge>
+</code></pre><p>In the above example we have shown all the parameters its
possible to
+configure for a bridge. In practice you might use many of the defaults
+so it won't be necessary to specify them all explicitly.</p>
+<p>Let's take a look at all the parameters in turn:</p>
+<ul>
+<li><p><code>name</code> attribute. All bridges must have a unique name in the
server.</p>
+</li>
+<li><p><code>queue-name</code>. This is the unique name of the local queue
that the
+bridge consumes from, it's a mandatory parameter.</p>
+<p>The queue must already exist by the time the bridge is instantiated
+at start-up.</p>
+<blockquote>
+<p><strong>Note</strong></p>
+<p>If you're using JMS then normally the JMS configuration
+<code>activemq-jms.xml</code> is loaded after the core configuration file
+<code>broker.xml</code> is loaded. If your bridge is
+consuming from a JMS queue then you'll need to make sure the JMS
+queue is also deployed as a core queue in the core configuration.
+Take a look at the bridge example for an example of how this is
+done.</p>
+</blockquote>
+</li>
+<li><p><code>forwarding-address</code>. This is the address on the target
server that
+the message will be forwarded to. If a forwarding address is not
+specified, then the original address of the message will be
+retained.</p>
+</li>
+<li><p><code>filter-string</code>. An optional filter string can be supplied.
If
+specified then only messages which match the filter expression
+specified in the filter string will be forwarded. The filter string
+follows the ActiveMQ Artemis filter expression syntax described in <a
href="filter-expressions.html">Filter Expressions</a>.</p>
+</li>
+<li><p><code>transformer-class-name</code>. An optional transformer-class-name
can be
+specified. This is the name of a user-defined class which implements
+the <code>org.apache.activemq.artemis.core.server.cluster.Transformer</code>
interface.</p>
+<p>If this is specified then the transformer's <code>transform()</code>
method
+will be invoked with the message before it is forwarded. This gives
+you the opportunity to transform the message's header or body before
+forwarding it.</p>
+</li>
+<li><p><code>ha</code>. This optional parameter determines whether or not this
bridge
+should support high availability. True means it will connect to any
+available server in a cluster and support failover. The default
+value is <code>false</code>.</p>
+</li>
+<li><p><code>retry-interval</code>. This optional parameter determines the
period in
+milliseconds between subsequent reconnection attempts, if the
+connection to the target server has failed. The default value is
+<code>2000</code>milliseconds.</p>
+</li>
+<li><p><code>retry-interval-multiplier</code>. This optional parameter
determines
+determines a multiplier to apply to the time since the last retry to
+compute the time to the next retry.</p>
+<p>This allows you to implement an <em>exponential backoff</em> between retry
+attempts.</p>
+<p>Let's take an example:</p>
+<p>If we set <code>retry-interval</code>to <code>1000</code> ms and we set
+<code>retry-interval-multiplier</code> to <code>2.0</code>, then, if the first
reconnect
+attempt fails, we will wait <code>1000</code> ms then <code>2000</code> ms
then <code>4000</code> ms
+between subsequent reconnection attempts.</p>
+<p>The default value is <code>1.0</code> meaning each reconnect attempt is
spaced
+at equal intervals.</p>
+</li>
+<li><p><code>initial-connect-attempts</code>. This optional parameter
determines the
+total number of initial connect attempts the bridge will make before
+giving up and shutting down. A value of <code>-1</code> signifies an unlimited
+number of attempts. The default value is <code>-1</code>.</p>
+</li>
+<li><p><code>reconnect-attempts</code>. This optional parameter determines the
total
+number of reconnect attempts the bridge will make before giving up
+and shutting down. A value of <code>-1</code> signifies an unlimited number of
+attempts. The default value is <code>-1</code>.</p>
+</li>
+<li><p><code>failover-on-server-shutdown</code>. This optional parameter
determines
+whether the bridge will attempt to failover onto a backup server (if
+specified) when the target server is cleanly shutdown rather than
+crashed.</p>
+<p>The bridge connector can specify both a live and a backup server, if
+it specifies a backup server and this parameter is set to <code>true</code>
+then if the target server is <em>cleanly</em> shutdown the bridge
+connection will attempt to failover onto its backup. If the bridge
+connector has no backup server configured then this parameter has no
+effect.</p>
+<p>Sometimes you want a bridge configured with a live and a backup
+target server, but you don't want to failover to the backup if the
+live server is simply taken down temporarily for maintenance, this
+is when this parameter comes in handy.</p>
+<p>The default value for this parameter is <code>false</code>.</p>
+</li>
+<li><p><code>use-duplicate-detection</code>. This optional parameter determines
+whether the bridge will automatically insert a duplicate id property
+into each message that it forwards.</p>
+<p>Doing so, allows the target server to perform duplicate detection on
+messages it receives from the source server. If the connection fails
+or server crashes, then, when the bridge resumes it will resend
+unacknowledged messages. This might result in duplicate messages
+being sent to the target server. By enabling duplicate detection
+allows these duplicates to be screened out and ignored.</p>
+<p>This allows the bridge to provide a <em>once and only once</em> delivery
+guarantee without using heavyweight methods such as XA (see <a
href="duplicate-detection.html">Duplicate Detection</a> for
+more information).</p>
+<p>The default value for this parameter is <code>true</code>.</p>
+</li>
+<li><p><code>confirmation-window-size</code>. This optional parameter
determines the
+<code>confirmation-window-size</code> to use for the connection used to forward
+messages to the target node. This attribute is described in section
+<a href="client-reconnection.html">Reconnection and Session
Reattachment</a></p>
+<blockquote>
+<p><strong>Warning</strong></p>
+<p>When using the bridge to forward messages to an address which uses
+the <code>BLOCK</code> <code>address-full-policy</code> from a queue which has
a
+<code>max-size-bytes</code> set it's important that
+<code>confirmation-window-size</code> is less than or equal to
+<code>max-size-bytes</code> to prevent the flow of messages from ceasing.</p>
+</blockquote>
+</li>
+<li><p><code>producer-window-size</code>. This optional parameter determines
the
+producer flow control through the bridge. You usually leave this off
+unless you are dealing with huge large messages. </p>
+<p>Default=-1 (disabled)</p>
+</li>
+<li><p><code>user</code>. This optional parameter determines the user name to
use when
+creating the bridge connection to the remote server. If it is not
+specified the default cluster user specified by <code>cluster-user</code> in
+<code>broker.xml</code> will be used.</p>
+</li>
+<li><p><code>password</code>. This optional parameter determines the password
to use
+when creating the bridge connection to the remote server. If it is
+not specified the default cluster password specified by
+<code>cluster-password</code> in <code>broker.xml</code> will be used.</p>
+</li>
+<li><p><code>static-connectors</code> or <code>discovery-group-ref</code>.
Pick either of these
+options to connect the bridge to the target server.</p>
+<p>The <code>static-connectors</code> is a list of <code>connector-ref</code>
elements
+pointing to <code>connector</code> elements defined elsewhere. A
<em>connector</em>
+encapsulates knowledge of what transport to use (TCP, SSL, HTTP etc)
+as well as the server connection parameters (host, port etc). For
+more information about what connectors are and how to configure
+them, please see <a href="configuring-transports.html">Configuring the
Transport</a>.</p>
+<p>The <code>discovery-group-ref</code> element has one attribute -
+<code>discovery-group-name</code>. This attribute points to a
<code>discovery-group</code>
+defined elsewhere. For more information about what discovery-groups
+are and how to configure them, please see <a href="clusters.html">Discovery
Groups</a>.</p>
+</li>
+</ul>
+
+
+ </section>
+
+ </div>
+ <div class="search-results">
+ <div class="has-results">
+
+ <h1 class="search-results-title"><span
class='search-results-count'></span> results matching "<span
class='search-query'></span>"</h1>
+ <ul class="search-results-list"></ul>
+
+ </div>
+ <div class="no-results">
+
+ <h1 class="search-results-title">No results matching "<span
class='search-query'></span>"</h1>
+
+ </div>
+ </div>
+</div>
+
+ </div>
+ </div>
+
+ </div>
+
+
+
+ <a href="diverts.html" class="navigation navigation-prev "
aria-label="Previous page: Diverting and Splitting Message Flows">
+ <i class="fa fa-angle-left"></i>
+ </a>
+
+
+ <a href="duplicate-detection.html" class="navigation
navigation-next " aria-label="Next page: Duplicate Message Detection">
+ <i class="fa fa-angle-right"></i>
+ </a>
+
+
+
+ </div>
+
+ <script>
+ var gitbook = gitbook || [];
+ gitbook.push(function() {
+ gitbook.page.hasChanged({"page":{"title":"Core
Bridges","level":"1.39","depth":1,"next":{"title":"Duplicate Message
Detection","level":"1.40","depth":1,"path":"duplicate-detection.md","ref":"duplicate-detection.md","articles":[]},"previous":{"title":"Diverting
and Splitting Message
Flows","level":"1.38","depth":1,"path":"diverts.md","ref":"diverts.md","articles":[]},"dir":"ltr"},"config":{"plugins":[],"styles":{"website":"styles/website.css","pdf":"styles/pdf.css","epub":"styles/epub.css","mobi":"styles/mobi.css","ebook":"styles/ebook.css","print":"styles/print.css"},"pluginsConfig":{"highlight":{},"search":{},"lunr":{"maxIndexSize":1000000},"sharing":{"facebook":true,"twitter":true,"google":false,"weibo":false,"instapaper":false,"vk":false,"all":["facebook","google","twitter","weibo","instapaper"]},"fontsettings":{"theme":"white","family":"sans","size":2},"theme-default":{"styles":{"website":"styles/website.css","pdf":"styles/pdf.css","epub":"styles/epub.css","mobi":"st
yles/mobi.css","ebook":"styles/ebook.css","print":"styles/print.css"},"showLevel":false}},"github":"apache/activemq-artemis","theme":"default","githubHost":"https://github.com/","pdf":{"pageNumbers":true,"fontSize":12,"fontFamily":"Arial","paperSize":"a4","chapterMark":"pagebreak","pageBreaksBefore":"/","margin":{"right":62,"left":62,"top":56,"bottom":56}},"structure":{"langs":"LANGS.md","readme":"README.md","glossary":"GLOSSARY.md","summary":"SUMMARY.md"},"variables":{},"title":"ActiveMQ
Artemis
Documentation","links":{"home":"http://activemq.apache.org/","issues":"http://activemq.apache.org/","contribute":"http://activemq.apache.org/contributing.html"},"gitbook":"3.x.x","description":"ActiveMQ
Artemis User Guide and Reference
Documentation"},"file":{"path":"core-bridges.md","mtime":"2016-10-22T12:23:36.000Z","type":"markdown"},"gitbook":{"version":"3.1.1","time":"2016-11-12T01:00:04.718Z"},"basePath":".","book":{"language":""}});
+ });
+ </script>
+</div>
+
+
+ <script src="gitbook/gitbook.js"></script>
+ <script src="gitbook/theme.js"></script>
+
+
+ <script src="gitbook/gitbook-plugin-search/search-engine.js"></script>
+
+
+
+ <script src="gitbook/gitbook-plugin-search/search.js"></script>
+
+
+
+ <script src="gitbook/gitbook-plugin-lunr/lunr.min.js"></script>
+
+
+
+ <script src="gitbook/gitbook-plugin-lunr/search-lunr.js"></script>
+
+
+
+ <script src="gitbook/gitbook-plugin-sharing/buttons.js"></script>
+
+
+
+ <script
src="gitbook/gitbook-plugin-fontsettings/fontsettings.js"></script>
+
+
+
+ </body>
+</html>
+
Added:
websites/production/activemq/content/artemis/docs/1.5.4/diagrams/architecture-diagrams.odg
==============================================================================
Binary file - no diff available.
Propchange:
websites/production/activemq/content/artemis/docs/1.5.4/diagrams/architecture-diagrams.odg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added:
websites/production/activemq/content/artemis/docs/1.5.4/diagrams/ha-colocated.odg
==============================================================================
Binary file - no diff available.
Propchange:
websites/production/activemq/content/artemis/docs/1.5.4/diagrams/ha-colocated.odg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added:
websites/production/activemq/content/artemis/docs/1.5.4/diagrams/ha-replicated-store.odg
==============================================================================
Binary file - no diff available.
Propchange:
websites/production/activemq/content/artemis/docs/1.5.4/diagrams/ha-replicated-store.odg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added:
websites/production/activemq/content/artemis/docs/1.5.4/diagrams/ha-scaledown.odg
==============================================================================
Binary file - no diff available.
Propchange:
websites/production/activemq/content/artemis/docs/1.5.4/diagrams/ha-scaledown.odg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added:
websites/production/activemq/content/artemis/docs/1.5.4/diagrams/ha-shared-store.odg
==============================================================================
Binary file - no diff available.
Propchange:
websites/production/activemq/content/artemis/docs/1.5.4/diagrams/ha-shared-store.odg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: websites/production/activemq/content/artemis/docs/1.5.4/diverts.html
==============================================================================
--- websites/production/activemq/content/artemis/docs/1.5.4/diverts.html (added)
+++ websites/production/activemq/content/artemis/docs/1.5.4/diverts.html Sun
Mar 12 16:08:18 2017
@@ -0,0 +1,1089 @@
+
+<!DOCTYPE HTML>
+<html lang="" >
+ <head>
+ <title>Diverting and Splitting Message Flows · ActiveMQ Artemis
Documentation</title>
+ <meta charset="UTF-8">
+ <meta http-equiv="X-UA-Compatible" content="IE=edge" />
+ <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
+ <meta name="description" content="">
+ <meta name="generator" content="GitBook 3.1.1">
+
+
+
+
+ <link rel="stylesheet" href="gitbook/style.css">
+
+
+
+
+ <link rel="stylesheet"
href="gitbook/gitbook-plugin-highlight/website.css">
+
+
+
+ <link rel="stylesheet"
href="gitbook/gitbook-plugin-search/search.css">
+
+
+
+ <link rel="stylesheet"
href="gitbook/gitbook-plugin-fontsettings/website.css">
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ <meta name="HandheldFriendly" content="true"/>
+ <meta name="viewport" content="width=device-width, initial-scale=1,
user-scalable=no">
+ <meta name="apple-mobile-web-app-capable" content="yes">
+ <meta name="apple-mobile-web-app-status-bar-style" content="black">
+ <link rel="apple-touch-icon-precomposed" sizes="152x152"
href="gitbook/images/apple-touch-icon-precomposed-152.png">
+ <link rel="shortcut icon" href="gitbook/images/favicon.ico"
type="image/x-icon">
+
+
+ <link rel="next" href="core-bridges.html" />
+
+
+ <link rel="prev" href="client-reconnection.html" />
+
+
+ </head>
+ <body>
+
+<div class="book">
+ <div class="book-summary">
+
+
+<div id="book-search-input" role="search">
+ <input type="text" placeholder="Type to search" />
+</div>
+
+
+ <nav role="navigation">
+
+
+
+<ul class="summary">
+
+
+
+
+
+
+
+
+
+ <li class="chapter " data-level="1.1" data-path="./">
+
+ <a href="./">
+
+
+ Introduction
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.2" data-path="notice.html">
+
+ <a href="notice.html">
+
+
+ Legal Notice
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.3" data-path="preface.html">
+
+ <a href="preface.html">
+
+
+ Preface
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.4" data-path="project-info.html">
+
+ <a href="project-info.html">
+
+
+ Project Info
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.5"
data-path="messaging-concepts.html">
+
+ <a href="messaging-concepts.html">
+
+
+ Messaging Concepts
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.6" data-path="architecture.html">
+
+ <a href="architecture.html">
+
+
+ Architecture
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.7" data-path="using-server.html">
+
+ <a href="using-server.html">
+
+
+ Using the Server
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.8" data-path="using-jms.html">
+
+ <a href="using-jms.html">
+
+
+ Using JMS
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.9" data-path="using-core.html">
+
+ <a href="using-core.html">
+
+
+ Using Core
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.10"
data-path="jms-core-mapping.html">
+
+ <a href="jms-core-mapping.html">
+
+
+ Mapping JMS Concepts to the Core API
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.11"
data-path="client-classpath.html">
+
+ <a href="client-classpath.html">
+
+
+ The Client Classpath
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.12" data-path="examples.html">
+
+ <a href="examples.html">
+
+
+ Examples
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.13"
data-path="wildcard-routing.html">
+
+ <a href="wildcard-routing.html">
+
+
+ Routing Messages With Wild Cards
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.14"
data-path="wildcard-syntax.html">
+
+ <a href="wildcard-syntax.html">
+
+
+ Understanding the Apache ActiveMQ Artemis Wildcard Syntax
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.15"
data-path="filter-expressions.html">
+
+ <a href="filter-expressions.html">
+
+
+ Filter Expressions
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.16" data-path="persistence.html">
+
+ <a href="persistence.html">
+
+
+ Persistence
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.17"
data-path="configuring-transports.html">
+
+ <a href="configuring-transports.html">
+
+
+ Configuring Transports
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.18" data-path="config-reload.html">
+
+ <a href="config-reload.html">
+
+
+ Configuration Reload
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.19" data-path="connection-ttl.html">
+
+ <a href="connection-ttl.html">
+
+
+ Detecting Dead Connections
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.20" data-path="slow-consumers.html">
+
+ <a href="slow-consumers.html">
+
+
+ Detecting Slow Consumers
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.21"
data-path="transaction-config.html">
+
+ <a href="transaction-config.html">
+
+
+ Resource Manager Configuration
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.22" data-path="flow-control.html">
+
+ <a href="flow-control.html">
+
+
+ Flow Control
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.23"
data-path="send-guarantees.html">
+
+ <a href="send-guarantees.html">
+
+
+ Guarantees of sends and commits
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.24"
data-path="undelivered-messages.html">
+
+ <a href="undelivered-messages.html">
+
+
+ Message Redelivery and Undelivered Messages
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.25" data-path="message-expiry.html">
+
+ <a href="message-expiry.html">
+
+
+ Message Expiry
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.26" data-path="large-messages.html">
+
+ <a href="large-messages.html">
+
+
+ Large Messages
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.27" data-path="paging.html">
+
+ <a href="paging.html">
+
+
+ Paging
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.28"
data-path="queue-attributes.html">
+
+ <a href="queue-attributes.html">
+
+
+ Queue Attributes
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.29"
data-path="scheduled-messages.html">
+
+ <a href="scheduled-messages.html">
+
+
+ Scheduled Messages
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.30"
data-path="last-value-queues.html">
+
+ <a href="last-value-queues.html">
+
+
+ Last-Value Queues
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.31"
data-path="message-grouping.html">
+
+ <a href="message-grouping.html">
+
+
+ Message Grouping
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.32"
data-path="pre-acknowledge.html">
+
+ <a href="pre-acknowledge.html">
+
+
+ Extra Acknowledge Modes
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.33" data-path="management.html">
+
+ <a href="management.html">
+
+
+ Management
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.34" data-path="security.html">
+
+ <a href="security.html">
+
+
+ Security
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.35"
data-path="resource-limits.html">
+
+ <a href="resource-limits.html">
+
+
+ Resource Limits
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.36" data-path="jms-bridge.html">
+
+ <a href="jms-bridge.html">
+
+
+ The JMS Bridge
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.37"
data-path="client-reconnection.html">
+
+ <a href="client-reconnection.html">
+
+
+ Client Reconnection and Session Reattachment
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter active" data-level="1.38" data-path="diverts.html">
+
+ <a href="diverts.html">
+
+
+ Diverting and Splitting Message Flows
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.39" data-path="core-bridges.html">
+
+ <a href="core-bridges.html">
+
+
+ Core Bridges
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.40"
data-path="duplicate-detection.html">
+
+ <a href="duplicate-detection.html">
+
+
+ Duplicate Message Detection
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.41" data-path="clusters.html">
+
+ <a href="clusters.html">
+
+
+ Clusters
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.42" data-path="ha.html">
+
+ <a href="ha.html">
+
+
+ High Availability and Failover
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.43"
data-path="graceful-shutdown.html">
+
+ <a href="graceful-shutdown.html">
+
+
+ Graceful Server Shutdown
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.44" data-path="libaio.html">
+
+ <a href="libaio.html">
+
+
+ Libaio Native Libraries
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.45" data-path="thread-pooling.html">
+
+ <a href="thread-pooling.html">
+
+
+ Thread management
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.46" data-path="logging.html">
+
+ <a href="logging.html">
+
+
+ Logging
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.47" data-path="rest.html">
+
+ <a href="rest.html">
+
+
+ REST Interface
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.48"
data-path="embedding-activemq.html">
+
+ <a href="embedding-activemq.html">
+
+
+ Embedding Apache ActiveMQ Artemis
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.49" data-path="karaf.html">
+
+ <a href="karaf.html">
+
+
+ Apache Karaf
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.50"
data-path="spring-integration.html">
+
+ <a href="spring-integration.html">
+
+
+ Spring Integration
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.51"
data-path="aerogear-integration.html">
+
+ <a href="aerogear-integration.html">
+
+
+ AeroGear Integration
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.52"
data-path="vertx-integration.html">
+
+ <a href="vertx-integration.html">
+
+
+ VertX Integration
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.53"
data-path="cdi-integration.html">
+
+ <a href="cdi-integration.html">
+
+
+ CDI Integration
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.54"
data-path="intercepting-operations.html">
+
+ <a href="intercepting-operations.html">
+
+
+ Intercepting Operations
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.55"
data-path="protocols-interoperability.html">
+
+ <a href="protocols-interoperability.html">
+
+
+ Protocols and Interoperability
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.56" data-path="tools.html">
+
+ <a href="tools.html">
+
+
+ Tools
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.57" data-path="maven-plugin.html">
+
+ <a href="maven-plugin.html">
+
+
+ Maven Plugin
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.58" data-path="unit-testing.html">
+
+ <a href="unit-testing.html">
+
+
+ Unit Testing
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.59" data-path="perf-tuning.html">
+
+ <a href="perf-tuning.html">
+
+
+ Troubleshooting and Performance Tuning
+
+ </a>
+
+
+
+ </li>
+
+ <li class="chapter " data-level="1.60"
data-path="configuration-index.html">
+
+ <a href="configuration-index.html">
+
+
+ Configuration Reference
+
+ </a>
+
+
+
+ </li>
+
+
+
+
+ <li class="divider"></li>
+
+ <li>
+ <a href="https://www.gitbook.com"; target="blank" class="gitbook-link">
+ Published with GitBook
+ </a>
+ </li>
+</ul>
+
+
+ </nav>
+
+
+ </div>
+
+ <div class="book-body">
+
+ <div class="body-inner">
+
+
+
+<div class="book-header" role="navigation">
+
+
+ <!-- Title -->
+ <h1>
+ <i class="fa fa-circle-o-notch fa-spin"></i>
+ <a href="." >Diverting and Splitting Message Flows</a>
+ </h1>
+</div>
+
+
+
+
+ <div class="page-wrapper" tabindex="-1" role="main">
+ <div class="page-inner">
+
+<div id="book-search-results">
+ <div class="search-noresults">
+
+ <section class="normal markdown-section">
+
+ <h1
id="diverting-and-splitting-message-flows">Diverting and Splitting Message
Flows</h1>
+<p>Apache ActiveMQ Artemis allows you to configure objects called
<em>diverts</em> with some
+simple server configuration.</p>
+<p>Diverts allow you to transparently divert messages routed to one address
+to some other address, without making any changes to any client
+application logic.</p>
+<p>Diverts can be <em>exclusive</em>, meaning that the message is diverted to
the
+new address, and does not go to the old address at all, or they can be
+<em>non-exclusive</em> which means the message continues to go the old address,
+and a <em>copy</em> of it is also sent to the new address. Non-exclusive
+diverts can therefore be used for <em>splitting</em> message flows, e.g. there
+may be a requirement to monitor every order sent to an order queue.</p>
+<p>Diverts can also be configured to have an optional message filter. If
+specified then only messages that match the filter will be diverted.</p>
+<p>When an address has both exclusive and non-exclusive diverts configured,
+the exclusive ones are processed first. If any of the exclusive diverts
+diverted the message, the non-exclusive ones are not processed.</p>
+<p>Diverts can also be configured to apply a <code>Transformer</code>. If
specified,
+all diverted messages will have the opportunity of being transformed by
+the <code>Transformer</code>. When an address has multiple diverts configured,
all
+of them receive the same, original message. This means that the results
+of a transformer on a message are not directly available for other
+diverts or their filters on the same address.</p>
+<p>A divert will only divert a message to an address on the <em>same
server</em>,
+however, if you want to divert to an address on a different server, a
+common pattern would be to divert to a local store-and-forward queue,
+then set up a bridge which consumes from that queue and forwards to an
+address on a different server.</p>
+<p>Diverts are therefore a very sophisticated concept, which when combined
+with bridges can be used to create interesting and complex routings. The
+set of diverts on a server can be thought of as a type of routing table
+for messages. Combining diverts with bridges allows you to create a
+distributed network of reliable routing connections between multiple
+geographically distributed servers, creating your global messaging mesh.</p>
+<p>Diverts are defined as xml in the <code>broker.xml</code> file.
+There can be zero or more diverts in the file.</p>
+<p>Please see the examples for a full working example showing you how to
+configure and use diverts.</p>
+<p>Let's take a look at some divert examples:</p>
+<h2 id="exclusive-divert">Exclusive Divert</h2>
+<p>Let's take a look at an exclusive divert. An exclusive divert diverts
+all matching messages that are routed to the old address to the new
+address. Matching messages do not get routed to the old address.</p>
+<p>Here's some example xml configuration for an exclusive divert,
it's
+taken from the divert example:</p>
+<pre><code><divert name="prices-divert">
+ <address>jms.topic.priceUpdates</address>
+
<forwarding-address>jms.queue.priceForwarding</forwarding-address>
+ <filter string="office='New York'"/>
+ <transformer-class-name>
+ org.apache.activemq.artemis.jms.example.AddForwardingTimeTransformer
+ </transformer-class-name>
+ <exclusive>true</exclusive>
+</divert>
+</code></pre><p>We define a divert called
'<code>prices-divert</code>' that will divert any
+messages sent to the address '<code>jms.topic.priceUpdates</code>'
(this
+corresponds to any messages sent to a JMS Topic called
'<code>priceUpdates</code>')
+to another local address '<code>jms.queue.priceForwarding</code>'
(this corresponds
+to a local JMS queue called '<code>priceForwarding</code>'</p>
+<p>We also specify a message filter string so only messages with the
+message property <code>office</code> with value <code>New York</code> will get
diverted, all
+other messages will continue to be routed to the normal address. The
+filter string is optional, if not specified then all messages will be
+considered matched.</p>
+<p>In this example a transformer class is specified. Again this is
+optional, and if specified the transformer will be executed for each
+matching message. This allows you to change the messages body or
+properties before it is diverted. In this example the transformer simply
+adds a header that records the time the divert happened.</p>
+<p>This example is actually diverting messages to a local store and forward
+queue, which is configured with a bridge which forwards the message to
+an address on another ActiveMQ Artemis server. Please see the example for more
+details.</p>
+<h2 id="non-exclusive-divert">Non-exclusive Divert</h2>
+<p>Now we'll take a look at a non-exclusive divert. Non exclusive diverts
+are the same as exclusive diverts, but they only forward a <em>copy</em> of the
+message to the new address. The original message continues to the old
+address</p>
+<p>You can therefore think of non-exclusive diverts as <em>splitting</em> a
+message flow.</p>
+<p>Non exclusive diverts can be configured in the same way as exclusive
+diverts with an optional filter and transformer, here's an example
+non-exclusive divert, again from the divert example:</p>
+<pre><code><divert name="order-divert">
+ <address>jms.queue.orders</address>
+ <forwarding-address>jms.topic.spyTopic</forwarding-address>
+ <exclusive>false</exclusive>
+</divert>
+</code></pre><p>The above divert example takes a copy of every message sent to
the
+address '<code>jms.queue.orders</code>' (Which corresponds to a JMS
Queue called
+'<code>orders</code>') and sends it to a local address called
+'<code>jms.topic.SpyTopic</code>' (which corresponds to a JMS Topic
called
+'<code>SpyTopic</code>').</p>
+
+
+ </section>
+
+ </div>
+ <div class="search-results">
+ <div class="has-results">
+
+ <h1 class="search-results-title"><span
class='search-results-count'></span> results matching "<span
class='search-query'></span>"</h1>
+ <ul class="search-results-list"></ul>
+
+ </div>
+ <div class="no-results">
+
+ <h1 class="search-results-title">No results matching "<span
class='search-query'></span>"</h1>
+
+ </div>
+ </div>
+</div>
+
+ </div>
+ </div>
+
+ </div>
+
+
+
+ <a href="client-reconnection.html" class="navigation
navigation-prev " aria-label="Previous page: Client Reconnection and Session
Reattachment">
+ <i class="fa fa-angle-left"></i>
+ </a>
+
+
+ <a href="core-bridges.html" class="navigation navigation-next
" aria-label="Next page: Core Bridges">
+ <i class="fa fa-angle-right"></i>
+ </a>
+
+
+
+ </div>
+
+ <script>
+ var gitbook = gitbook || [];
+ gitbook.push(function() {
+ gitbook.page.hasChanged({"page":{"title":"Diverting and Splitting
Message Flows","level":"1.38","depth":1,"next":{"title":"Core
Bridges","level":"1.39","depth":1,"path":"core-bridges.md","ref":"core-bridges.md","articles":[]},"previous":{"title":"Client
Reconnection and Session
Reattachment","level":"1.37","depth":1,"path":"client-reconnection.md","ref":"client-reconnection.md","articles":[]},"dir":"ltr"},"config":{"plugins":[],"styles":{"website":"styles/website.css","pdf":"styles/pdf.css","epub":"styles/epub.css","mobi":"styles/mobi.css","ebook":"styles/ebook.css","print":"styles/print.css"},"pluginsConfig":{"highlight":{},"search":{},"lunr":{"maxIndexSize":1000000},"sharing":{"facebook":true,"twitter":true,"google":false,"weibo":false,"instapaper":false,"vk":false,"all":["facebook","google","twitter","weibo","instapaper"]},"fontsettings":{"theme":"white","family":"sans","size":2},"theme-default":{"styles":{"website":"styles/website.css","pdf":"styles/pdf.css","epub":"
styles/epub.css","mobi":"styles/mobi.css","ebook":"styles/ebook.css","print":"styles/print.css"},"showLevel":false}},"github":"apache/activemq-artemis","theme":"default","githubHost":"https://github.com/","pdf":{"pageNumbers":true,"fontSize":12,"fontFamily":"Arial","paperSize":"a4","chapterMark":"pagebreak","pageBreaksBefore":"/","margin":{"right":62,"left":62,"top":56,"bottom":56}},"structure":{"langs":"LANGS.md","readme":"README.md","glossary":"GLOSSARY.md","summary":"SUMMARY.md"},"variables":{},"title":"ActiveMQ
Artemis
Documentation","links":{"home":"http://activemq.apache.org/","issues":"http://activemq.apache.org/","contribute":"http://activemq.apache.org/contributing.html"},"gitbook":"3.x.x","description":"ActiveMQ
Artemis User Guide and Reference
Documentation"},"file":{"path":"diverts.md","mtime":"2016-10-22T12:23:36.000Z","type":"markdown"},"gitbook":{"version":"3.1.1","time":"2016-11-12T01:00:04.718Z"},"basePath":".","book":{"language":""}});
+ });
+ </script>
+</div>
+
+
+ <script src="gitbook/gitbook.js"></script>
+ <script src="gitbook/theme.js"></script>
+
+
+ <script src="gitbook/gitbook-plugin-search/search-engine.js"></script>
+
+
+
+ <script src="gitbook/gitbook-plugin-search/search.js"></script>
+
+
+
+ <script src="gitbook/gitbook-plugin-lunr/lunr.min.js"></script>
+
+
+
+ <script src="gitbook/gitbook-plugin-lunr/search-lunr.js"></script>
+
+
+
+ <script src="gitbook/gitbook-plugin-sharing/buttons.js"></script>
+
+
+
+ <script
src="gitbook/gitbook-plugin-fontsettings/fontsettings.js"></script>
+
+
+
+ </body>
+</html>
+
