You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by gi...@apache.org on 2021/12/01 01:58:28 UTC
[activemq-website] branch asf-site updated: Automatic Site Publish by Buildbot
This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/activemq-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 48ab6a1 Automatic Site Publish by Buildbot
48ab6a1 is described below
commit 48ab6a192d0d63f5a99dce9317f7a0eaa8632ccd
Author: buildbot <us...@infra.apache.org>
AuthorDate: Wed Dec 1 01:58:26 2021 +0000
Automatic Site Publish by Buildbot
---
output/discovery-transport-reference.html | 56 ++++++++++++++++++++++++++-----
output/fanout-transport-reference.html | 56 ++++++++++++++++++++++++++-----
2 files changed, 94 insertions(+), 18 deletions(-)
diff --git a/output/discovery-transport-reference.html b/output/discovery-transport-reference.html
index a1dd75d..cbbc0ff 100644
--- a/output/discovery-transport-reference.html
+++ b/output/discovery-transport-reference.html
@@ -118,15 +118,53 @@
</code></pre></div></div>
<h5 id="transport-options">Transport Options</h5>
-<p>Option Name|Default Value|Description
-—|—|—
-reconnectDelay|10|How long to wait for discovery
-initialReconnectDelay|10|How long to wait before the first reconnect attempt to a discovered url
-maxReconnectDelay|30000|The maximum amount of time we ever wait between reconnect attempts
-useExponentialBackOff|true|Should an exponential backoff be used btween reconnect attempts
-backOffMultiplier|2|The exponent used in the exponential backoff attempts
-maxReconnectAttempts|0|If not 0, then this is the maximum number of reconnect attempts before an error is sent back to the client
-group|default|an identifier for the group to partition multi cast traffic among collaborating peers; the group forms part of the shared identity of a discovery datagram (since 5.2)</p>
+
+<table>
+ <thead>
+ <tr>
+ <th>Option Name</th>
+ <th>Default Value</th>
+ <th>Description</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>reconnectDelay</td>
+ <td>10</td>
+ <td>How long to wait for discovery</td>
+ </tr>
+ <tr>
+ <td>initialReconnectDelay</td>
+ <td>10</td>
+ <td>How long to wait before the first reconnect attempt to a discovered url</td>
+ </tr>
+ <tr>
+ <td>maxReconnectDelay</td>
+ <td>30000</td>
+ <td>The maximum amount of time we ever wait between reconnect attempts</td>
+ </tr>
+ <tr>
+ <td>useExponentialBackOff</td>
+ <td>true</td>
+ <td>Should an exponential backoff be used btween reconnect attempts</td>
+ </tr>
+ <tr>
+ <td>backOffMultiplier</td>
+ <td>2</td>
+ <td>The exponent used in the exponential backoff attempts</td>
+ </tr>
+ <tr>
+ <td>maxReconnectAttempts</td>
+ <td>0</td>
+ <td>If not 0, then this is the maximum number of reconnect attempts before an error is sent back to the client</td>
+ </tr>
+ <tr>
+ <td>group</td>
+ <td>default</td>
+ <td>an identifier for the group to partition multi cast traffic among collaborating peers; the group forms part of the shared identity of a discovery datagram (since 5.2)</td>
+ </tr>
+ </tbody>
+</table>
<h5 id="example-uri">Example URI</h5>
<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>discovery:(multicast://default)?initialReconnectDelay=100
diff --git a/output/fanout-transport-reference.html b/output/fanout-transport-reference.html
index 0a89354..c04f7f5 100644
--- a/output/fanout-transport-reference.html
+++ b/output/fanout-transport-reference.html
@@ -105,15 +105,53 @@
</code></pre></div></div>
<h5 id="transport-options">Transport Options</h5>
-<p>Option Name|Default Value|Description
-—|—|—
-initialReconnectDelay|10|How long to wait before the first reconnect attempt
-maxReconnectDelay|30000|The maximum amount of time we ever wait between reconnect attempts
-useExponentialBackOff|true|Should an exponential backoff be used btween reconnect attempts
-backOffMultiplier|2|The exponent used in the exponential backoff attempts
-maxReconnectAttempts|0|If not 0, then this is the maximum number of reconnect attempts before an error is sent back to the client
-fanOutQueues|false|If set to ‘true’, commands are replicated to queues as well as topics
-minAckCount|2|The minimum number of brokers to which connections must be established</p>
+
+<table>
+ <thead>
+ <tr>
+ <th>Option Name</th>
+ <th>Default Value</th>
+ <th>Description</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>initialReconnectDelay</td>
+ <td>10</td>
+ <td>How long to wait before the first reconnect attempt</td>
+ </tr>
+ <tr>
+ <td>maxReconnectDelay</td>
+ <td>30000</td>
+ <td>The maximum amount of time we ever wait between reconnect attempts</td>
+ </tr>
+ <tr>
+ <td>useExponentialBackOff</td>
+ <td>true</td>
+ <td>Should an exponential backoff be used between reconnect attempts</td>
+ </tr>
+ <tr>
+ <td>backOffMultiplier</td>
+ <td>2</td>
+ <td>The exponent used in the exponential backoff attempts</td>
+ </tr>
+ <tr>
+ <td>maxReconnectAttempts</td>
+ <td>0</td>
+ <td>If not 0, then this is the maximum number of reconnect attempts before an error is sent back to the client</td>
+ </tr>
+ <tr>
+ <td>fanOutQueues</td>
+ <td>false</td>
+ <td>If set to ‘true’, commands are replicated to queues as well as topics</td>
+ </tr>
+ <tr>
+ <td>minAckCount</td>
+ <td>2</td>
+ <td>The minimum number of brokers to which connections must be established</td>
+ </tr>
+ </tbody>
+</table>
<p>The ‘fanOutQueues’ option is specific to the fanout transport. By default, the fanout does not replicate commands to queues; only topics. Therefore, if you’d like to fanout a message send command to multiple queues on multiple brokers, you’ll have to set this option to ‘true’.</p>