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 980c1587c Automatic Site Publish by Buildbot
980c1587c is described below
commit 980c1587c4f5d08eec854bae1dff6711c2925650
Author: buildbot <[email protected]>
AuthorDate: Thu May 2 09:43:00 2024 +0000
Automatic Site Publish by Buildbot
---
.../classic/documentation/failover-transport-reference.html | 8 ++++----
output/components/classic/documentation/kahadb-master-slave.html | 2 +-
output/components/classic/documentation/networks-of-brokers.html | 2 +-
.../classic/documentation/shared-file-system-master-slave.html | 2 +-
4 files changed, 7 insertions(+), 7 deletions(-)
diff --git
a/output/components/classic/documentation/failover-transport-reference.html
b/output/components/classic/documentation/failover-transport-reference.html
index e0924bd62..8a670541b 100644
--- a/output/components/classic/documentation/failover-transport-reference.html
+++ b/output/components/classic/documentation/failover-transport-reference.html
@@ -225,11 +225,11 @@
<p>The Failover transport tracks transactions by default. In-flight
transactions are replayed upon re-connection. For simple scenarios this works
as expected. However, there is an assumption regarding acknowledged (or
consumer) transactions in that the previously received messages will
automatically be replayed upon re-connection. This, however, is not always true
when there are many connections and consumers, as re-delivery order is not
guaranteed as stale outstanding acknowledgements c [...]
-<p><code class="language-plaintext highlighter-rouge">From ActiveMQ Classic
5.3.1**: re-delivery order **_is_** tracked and a transaction will fail to
commit if outstanding messages are not redelivered after failover. A
</code>javax.jms.``TransactionRolledBackException` is thrown if the commit
fails. In doubt transactions will result in a rollback such that they can be
replayed by the application. In doubt transactions occur when failover happens
when a commit message is in-flight. It is [...]
+<p><strong>From ActiveMQ Classic 5.3.1</strong>: re-delivery order
<strong><em>is</em></strong> tracked and a transaction will fail to commit if
outstanding messages are not redelivered after failover. A <code
class="language-plaintext
highlighter-rouge">javax.jms.TransactionRolledBackException</code> is thrown if
the commit fails. In doubt transactions will result in a rollback such that
they can be replayed by the application. In doubt transactions occur when
failover happens when a co [...]
<h5 id="broker-side-options-for-failover">Broker-side Options for Failover</h5>
-<p><code class="language-plaintext highlighter-rouge">From ActiveMQ Classic
5.4**: the </code>TransportConnector` has options available so that the broker
can update clients automatically with information regarding the presence of new
brokers that are available (or are no longer available) for failover.</p>
+<p><strong>From ActiveMQ Classic 5.4</strong>: the <code
class="language-plaintext highlighter-rouge">TransportConnector</code> has
options available so that the broker can update clients automatically with
information regarding the presence of new brokers that are available (or are no
longer available) for failover.</p>
<p>The options are:</p>
@@ -289,7 +289,7 @@
<h5 id="priority-backup">Priority Backup</h5>
-<p><code class="language-plaintext highlighter-rouge">From ActiveMQ Classic
5.6**: if brokers are available in both local and remote networks, it's
possible to specify a preference for local brokers over remote brokers using
the </code>priorityBackup<code class="language-plaintext highlighter-rouge">
and </code>priorityURIs` options.</p>
+<p><strong>From ActiveMQ Classic 5.6</strong>: if brokers are available in
both local and remote networks, it’s possible to specify a preference for local
brokers over remote brokers using the <code class="language-plaintext
highlighter-rouge">priorityBackup</code> and <code class="language-plaintext
highlighter-rouge">priorityURIs</code> options.</p>
<p>Consider the following URL:</p>
<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>failover:(tcp://local:61616,tcp://remote:61616)?randomize=false&priorityBackup=true
@@ -305,7 +305,7 @@
<h5 id="configuring-nested-uri-options">Configuring Nested URI Options.</h5>
-<p><code class="language-plaintext highlighter-rouge">From ActiveMQ Classic
5.9**: common URI options can be configured by appending them to the query
string of the failover URI where each common URI option has the prefix:
</code>nested.` </p>
+<p><strong>From ActiveMQ Classic 5.9</strong>: common URI options can be
configured by appending them to the query string of the failover URI where each
common URI option has the prefix: <code class="language-plaintext
highlighter-rouge">nested.</code> </p>
<p>Example - instead of doing this:</p>
<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>failover:(tcp://broker1:61616?wireFormat.maxInactivityDuration=1000,tcp://broker2:61616?wireFormat.maxInactivityDuration=1000,tcp://broker3:61616?wireFormat.maxInactivityDuration=1000)
diff --git a/output/components/classic/documentation/kahadb-master-slave.html
b/output/components/classic/documentation/kahadb-master-slave.html
index 900cf2822..f884d22f9 100644
--- a/output/components/classic/documentation/kahadb-master-slave.html
+++ b/output/components/classic/documentation/kahadb-master-slave.html
@@ -115,7 +115,7 @@
<h2 id="master-election">Master Election</h2>
-<p>KahaDB supports a pluggable Master Election algorithm but the only current
implementation is one based on <a
href="http://hadoop.apache.org/zookeeper";>ZooKeeper</a>.</p>
+<p>KahaDB supports a pluggable Master Election algorithm but the only current
implementation is one based on <a
href="https://zookeeper.apache.org/";>ZooKeeper</a>.</p>
<p>ZooKeeper is used to implement the master election algorithm. ZooKeeper is
a very fast, replicated, in memory database with features that make it easy to
implement cluster control algorithms. It is an Apache project which you can <a
href="http://hadoop.apache.org/zookeeper/releases.html";>freely download</a>.
You must installed and have at least one ZooKeeper server running before
setting up a KahaDB Master Slave configuration.</p>
diff --git a/output/components/classic/documentation/networks-of-brokers.html
b/output/components/classic/documentation/networks-of-brokers.html
index d41e29c77..49dfcbd7a 100644
--- a/output/components/classic/documentation/networks-of-brokers.html
+++ b/output/components/classic/documentation/networks-of-brokers.html
@@ -144,7 +144,7 @@
<h3 id="example-using-multicast-discovery">Example using multicast
discovery</h3>
-<p>This example uses multicast <a
href="http://activemq.apache.orgFeatures/discovery";>discovery</a></p>
+<p>This example uses <a href="discovery#multicast">multicast discovery</a></p>
<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code><?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://activemq.org/config/1.0">
diff --git
a/output/components/classic/documentation/shared-file-system-master-slave.html
b/output/components/classic/documentation/shared-file-system-master-slave.html
index 39a52082b..47b92de4c 100644
---
a/output/components/classic/documentation/shared-file-system-master-slave.html
+++
b/output/components/classic/documentation/shared-file-system-master-slave.html
@@ -157,7 +157,7 @@ See this JIRA for more discussion: <a
href="https://issues.apache.org/jira/brows
<p><img src="assets/img/MasterFailed.png" alt="" /></p>
-<p>One of the other other slaves immediately grabs the exclusive lock on the
file system to them commences becoming the master, starting all of its
transport connectors.</p>
+<p>One of the other slaves immediately grabs the exclusive lock on the file
system to them commences becoming the master, starting all of its transport
connectors.</p>
<p>Clients loose connection to the stopped master and then the failover
transport tries to connect to the available brokers - of which the only one
available is the new master.</p>
