activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r940038 - in /websites/production/activemq/content: cache/main.pageCache failover-transport-reference.html
Date Fri, 13 Feb 2015 11:21:24 GMT
Author: buildbot
Date: Fri Feb 13 11:21:24 2015
New Revision: 940038

Log:
Production update by buildbot for activemq

Modified:
    websites/production/activemq/content/cache/main.pageCache
    websites/production/activemq/content/failover-transport-reference.html

Modified: websites/production/activemq/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/activemq/content/failover-transport-reference.html
==============================================================================
--- websites/production/activemq/content/failover-transport-reference.html (original)
+++ websites/production/activemq/content/failover-transport-reference.html Fri Feb 13 11:21:24
2015
@@ -84,7 +84,7 @@
 <div class="wiki-content maincontent"><h3 id="FailoverTransportReference-TheFailoverTransport">The
Failover Transport</h3><p>The Failover transport layers reconnect logic on top
of any of the other transports. (We used to call this transport the Reliable transport in
ActiveMQ 3).</p><p>The Failover configuration syntax allows you to specify any
number of composite uris. The Failover transport randomly chooses one of the composite URI
and attempts to establish a connection to it. If it does not succeed or if it subsequently
fails, a new connection is established to one of the other uris in the list.</p><h4
id="FailoverTransportReference-ConfigurationSyntax">Configuration Syntax</h4><p><strong>failover:(uri1,...,uriN)?transportOptions</strong><br
clear="none"> or<br clear="none"> <strong>failover:uri1,...,uriN</strong></p><p>The
failover transport uses random by default which lets you to load balance clients over a number
of brokers.</p><p>If you would rather connect to a primary firs
 t and only connect to a secondary backup broker if the primary is unavailable, turn off randomizing
using something like</p><div class="preformatted panel" style="border-width: 1px;"><div
class="preformattedContent panelContent">
 <pre>failover:(tcp://primary:61616,tcp://secondary:61616)?randomize=false
 </pre>
-</div></div><h5 id="FailoverTransportReference-TransportOptions">Transport
Options</h5><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th
colspan="1" rowspan="1" class="confluenceTh"><p>Option Name</p></th><th
colspan="1" rowspan="1" class="confluenceTh"><p>Default Value</p></th><th
colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>initialReconnectDelay</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>10</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>How long to wait before the first reconnect attempt
(in ms)</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>maxReconnectDelay</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>30000</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The maximum amount of time we ever
wait between reconnect attempts (in ms)</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>use
 ExponentialBackOff</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Should an exponential backoff be
used btween reconnect attempts</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>reconnectDelayExponent</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>2.0</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>The exponent used in the exponential backoff
attempts</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>maxReconnectAttempts</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>-1 | 0</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>From version 5.6 onwards: -1 is default
and means retry forever, 0 means don't retry (only try connection once but no retry). <br
clear="none" class="atl-forced-newline"> Prior to version 5.6: 0 is default and means retry
forever. <br clear="none" class="atl-forced-newline"> All versions: If set to &g
 t;0, then this is the maximum number of reconnect attempts before an error is sent back to
the client.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>startupMaxReconnectAttempts</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>-1</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>If not 0, then this is the maximum number of
reconnect attempts before an error is sent back to the client on the first attempt by the
client to start a connection, once connected the <strong>maxReconnectAttempts</strong>
option takes precedence.&#160; A value of -1 signifies that the transport will have no
limit to the number of initial connection attempts.</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>randomize</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>use a random algorithm to choose the the URI
to use for reconnect from the list provided</p></td></tr><tr><td
  colspan="1" rowspan="1" class="confluenceTd"><p>backup</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>initialize and hold a second transport
connection - to enable fast failover</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>timeout</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>-1</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Enables timeout on send operations (in miliseconds) without
interruption of reconnection process</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>trackMessages</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>keep a cache of in-flight messages that will
flushed to a broker on reconnect</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>maxCacheSize</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>131072</p></t
 d><td colspan="1" rowspan="1" class="confluenceTd"><p>size in bytes for the
cache, if trackMessages is enabled</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>updateURIsSupported</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Determines whether the client should accept updates
to its list of known URIs from the connected broker. <strong>Added in ActiveMQ 5.4</strong></p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>updateURIsURL</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>A URL (or path to a local file) to a text file
containing a comma separated list of URIs to use for reconnect in the case of failure. <strong>Added
in ActiveMQ 5.4</strong></p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>nested.*</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>null</p><
 /td><td colspan="1" rowspan="1" class="confluenceTd"><p>Extra options to add
to the nested URLs. <strong>Added in ActiveMQ 5.9</strong></p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>warnAfterReconnectAttempts.*</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>10</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>After every N reconnect attempts log a warning
to indicate there is no connection but that we are still trying, set to &lt;= 0 to disable.
<strong>Added in ActiveMQ 5.10</strong></p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd">reconnectSupported</td><td colspan="1"
rowspan="1" class="confluenceTd">true</td><td colspan="1" rowspan="1" class="confluenceTd">Determines
whether the client should respond to broker ConnectionControl events with a reconnect (see:
<span>rebalanceClusterClients)</span></td></tr></tbody></table></div><h5
id="FailoverTransportReference-ExampleURI">Example URI</h5><div class="preformatted
panel
 " style="border-width: 1px;"><div class="preformattedContent panelContent">
+</div></div><h5 id="FailoverTransportReference-TransportOptions">Transport
Options</h5><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th
colspan="1" rowspan="1" class="confluenceTh"><p>Option Name</p></th><th
colspan="1" rowspan="1" class="confluenceTh"><p>Default Value</p></th><th
colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>initialReconnectDelay</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>10</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>How long to wait before the first reconnect attempt
(in ms)</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>maxReconnectDelay</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>30000</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The maximum amount of time we ever
wait between reconnect attempts (in ms)</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>use
 ExponentialBackOff</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Should an exponential backoff be
used btween reconnect attempts</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>reconnectDelayExponent</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>2.0</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>The exponent used in the exponential backoff
attempts</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>maxReconnectAttempts</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>-1 | 0</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>From version 5.6 onwards: -1 is default
and means retry forever, 0 means don't retry (only try connection once but no retry). <br
clear="none" class="atl-forced-newline"> Prior to version 5.6: 0 is default and means retry
forever. <br clear="none" class="atl-forced-newline"> All versions: If set to &g
 t;0, then this is the maximum number of reconnect attempts before an error is sent back to
the client.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>startupMaxReconnectAttempts</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>-1</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>If not 0, then this is the maximum number of
reconnect attempts before an error is sent back to the client on the first attempt by the
client to start a connection, once connected the <strong>maxReconnectAttempts</strong>
option takes precedence.&#160; A value of -1 signifies that the transport will have no
limit to the number of initial connection attempts.</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>randomize</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>use a random algorithm to choose the the URI
to use for reconnect from the list provided</p></td></tr><tr><td
  colspan="1" rowspan="1" class="confluenceTd"><p>backup</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>initialize and hold a second transport
connection - to enable fast failover</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>timeout</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>-1</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Enables timeout on send operations (in miliseconds) without
interruption of reconnection process</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>trackMessages</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>keep a cache of in-flight messages that will
flushed to a broker on reconnect</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>maxCacheSize</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>131072</p></t
 d><td colspan="1" rowspan="1" class="confluenceTd"><p>size in bytes for the
cache, if trackMessages is enabled</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>updateURIsSupported</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Determines whether the client should accept updates
to its list of known URIs from the connected broker. <strong>Added in ActiveMQ 5.4</strong></p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>updateURIsURL</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>A URL (or path to a local file) to a text file
containing a comma separated list of URIs to use for reconnect in the case of failure. <strong>Added
in ActiveMQ 5.4</strong></p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>nested.*</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>null</p><
 /td><td colspan="1" rowspan="1" class="confluenceTd"><p>Extra options to add
to the nested URLs. <strong>Added in ActiveMQ 5.9</strong></p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>warnAfterReconnectAttempts</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>10</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>After every N reconnect attempts log a warning
to indicate there is no connection but that we are still trying, set to &lt;= 0 to disable.
<strong>Added in ActiveMQ 5.10</strong></p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd">reconnectSupported</td><td colspan="1"
rowspan="1" class="confluenceTd">true</td><td colspan="1" rowspan="1" class="confluenceTd">Determines
whether the client should respond to broker ConnectionControl events with a reconnect (see:
<span>rebalanceClusterClients)</span></td></tr></tbody></table></div><h5
id="FailoverTransportReference-ExampleURI">Example URI</h5><div class="preformatted
panel" 
 style="border-width: 1px;"><div class="preformattedContent panelContent">
 <pre>failover:(tcp://localhost:61616,tcp://remotehost:61616)?initialReconnectDelay=100
 </pre>
 </div></div><p>If the above gives errors try it this way (this way works
in ActiveMQ 4.1.1 the one above does not)</p><div class="preformatted panel" style="border-width:
1px;"><div class="preformattedContent panelContent">



Mime
View raw message