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 e813ba586 Automatic Site Publish by Buildbot
e813ba586 is described below
commit e813ba586bb6146d293292e71641ed18fa8074ac
Author: buildbot <us...@infra.apache.org>
AuthorDate: Tue Jun 11 08:47:50 2024 +0000
Automatic Site Publish by Buildbot
---
.../classic/documentation/connection-configuration-uri.html | 10 +++++-----
.../classic/documentation/failover-transport-reference.html | 2 +-
.../how-can-i-monitor-the-connection-with-the-broker.html | 4 ++--
.../how-can-i-see-what-destinations-are-used.html | 4 ++--
.../classic/documentation/how-do-i-purge-a-queue.html | 4 ++--
.../classic/documentation/how-do-transactions-work.html | 4 ++--
output/components/classic/documentation/interceptors.html | 6 +++---
output/components/classic/documentation/jdbc-support.html | 2 +-
output/components/classic/documentation/jmx.html | 2 +-
.../classic/documentation/multicast-transport-reference.html | 2 +-
.../components/classic/documentation/new-features-in-513.html | 2 +-
output/components/classic/documentation/persistence.html | 2 +-
output/components/classic/documentation/security.html | 2 +-
output/components/classic/documentation/shiro.html | 4 ++--
output/components/classic/documentation/uri-protocols.html | 4 ++--
.../classic/documentation/what-is-the-prefetch-limit-for.html | 4 ++--
16 files changed, 29 insertions(+), 29 deletions(-)
diff --git
a/output/components/classic/documentation/connection-configuration-uri.html
b/output/components/classic/documentation/connection-configuration-uri.html
index b09461ed7..a79039641 100644
--- a/output/components/classic/documentation/connection-configuration-uri.html
+++ b/output/components/classic/documentation/connection-configuration-uri.html
@@ -96,11 +96,11 @@
<h2 id="connection-configuration-uri">Connection Configuration URI</h2>
-<p>An Apache ActiveMQ Classic connection can be configured by explicitly
setting properties on the <a
href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/ActiveMQConnection.html";>ActiveMQConnection</a>
or <a
href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/ActiveMQConnectionFactory.html";>ActiveMQConnectionFactory</a>
objects themselves via the bean properties or using the following URI
syntax.</p>
+<p>An Apache ActiveMQ Classic connection can be configured by explicitly
setting properties on the <a
href="http://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/ActiveMQConnection.html";>ActiveMQConnection</a>
or <a
href="http://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/ActiveMQConnectionFactory.html";>ActiveMQConnectionFactory</a>
objects themselves via the bean properties or using the following URI
syntax.</p>
<h3 id="example">Example</h3>
-<p>You set the property called <code class="language-plaintext
highlighter-rouge">jms.$PROPERTY</code> on a regular connection URI. For
example you can set the <code class="language-plaintext
highlighter-rouge">brokerURL</code> on your <a
href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/ActiveMQConnectionFactory.html";>ActiveMQConnectionFactory</a>
to the following value to enable <a href="async-sends">Async Sends</a></p>
+<p>You set the property called <code class="language-plaintext
highlighter-rouge">jms.$PROPERTY</code> on a regular connection URI. For
example you can set the <code class="language-plaintext
highlighter-rouge">brokerURL</code> on your <a
href="http://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/ActiveMQConnectionFactory.html";>ActiveMQConnectionFactory</a>
to the following value to enable <a href="async-sends">Async Sends</a></p>
<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>tcp://localhost:61616?jms.useAsyncSend=true
</code></pre></div></div>
@@ -249,17 +249,17 @@
<tbody>
<tr>
<td><code class="language-plaintext
highlighter-rouge">jms.blobTransferPolicy.*</code></td>
- <td><a
href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/blob/BlobTransferPolicy.html";>BlobTransferPolicy</a></td>
+ <td><a
href="http://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/blob/BlobTransferPolicy.html";>BlobTransferPolicy</a></td>
<td><a href="#">Blob Message</a></td>
</tr>
<tr>
<td><code class="language-plaintext
highlighter-rouge">jms.prefetchPolicy.*</code></td>
- <td><a
href="http://http//activemq.apache.org/maven/apidocs/org/apache/activemq/ActiveMQPrefetchPolicy.html";>ActiveMQPrefetchPolicy</a></td>
+ <td><a
href="http://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/ActiveMQPrefetchPolicy.html";>ActiveMQPrefetchPolicy</a></td>
<td><a href="what-is-the-prefetch-limit-for">What is the Prefetch Limit
For?</a></td>
</tr>
<tr>
<td><code class="language-plaintext
highlighter-rouge">jms.redeliveryPolicy.*</code></td>
- <td><a
href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/RedeliveryPolicy.html";>RedeliveryPolicy</a></td>
+ <td><a
href="http://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/RedeliveryPolicy.html";>RedeliveryPolicy</a></td>
<td><a href="redelivery-policy">Redelivery Policy</a></td>
</tr>
</tbody>
diff --git
a/output/components/classic/documentation/failover-transport-reference.html
b/output/components/classic/documentation/failover-transport-reference.html
index 8a670541b..908a5ceb1 100644
--- a/output/components/classic/documentation/failover-transport-reference.html
+++ b/output/components/classic/documentation/failover-transport-reference.html
@@ -214,7 +214,7 @@
<h5 id="notes">Notes</h5>
-<p>Under the Failover transport send operations will, by default, block
indefinitely when the broker becomes unavailable. There are two options
available for handling this scenario. First, either set a <a
href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/transport/TransportListener.html";>TransportListener</a>
directly on the <a
href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/ActiveMQConnectionFactory.html";>ActiveMQConnectionFactory</a>,
so that it is i [...]
+<p>Under the Failover transport send operations will, by default, block
indefinitely when the broker becomes unavailable. There are two options
available for handling this scenario. First, either set a <a
href="http://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/transport/TransportListener.html";>TransportListener</a>
directly on the <a
href="http://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/ActiveMQConn
[...]
<p>Example:</p>
<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>failover:(tcp://primary:61616)?timeout=3000
diff --git
a/output/components/classic/documentation/how-can-i-monitor-the-connection-with-the-broker.html
b/output/components/classic/documentation/how-can-i-monitor-the-connection-with-the-broker.html
index 1ebd98c31..64c8e2f32 100644
---
a/output/components/classic/documentation/how-can-i-monitor-the-connection-with-the-broker.html
+++
b/output/components/classic/documentation/how-can-i-monitor-the-connection-with-the-broker.html
@@ -96,9 +96,9 @@
<h2 id="how-can-i-monitor-the-connection-with-the-broker">How can I monitor
the connection with the broker</h2>
-<p>You can monitor the status of the connection with the broker via the <a
href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/ActiveMQConnection.html#addTransportListener%28org.apache.activemq.transport.TransportListener";>addTransportListener()
method on the ActiveMQConnection</a>.</p>
+<p>You can monitor the status of the connection with the broker via the <a
href="http://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/ActiveMQConnection.html#addTransportListener%28org.apache.activemq.transport.TransportListener";>addTransportListener()
method on the ActiveMQConnection</a>.</p>
-<p>This method takes a <a
href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/transport/TransportListener.html";>TransportListener</a>
which is notified as the connection is established & dropped. It also
allows you to work with the <a href="failover-transport-reference">Failover
Transport</a> yet still know the status of the connection.</p>
+<p>This method takes a <a
href="http://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/transport/TransportListener.html";>TransportListener</a>
which is notified as the connection is established & dropped. It also
allows you to work with the <a href="failover-transport-reference">Failover
Transport</a> yet still know the status of the connection.</p>
<h3 id="see-also">See Also</h3>
diff --git
a/output/components/classic/documentation/how-can-i-see-what-destinations-are-used.html
b/output/components/classic/documentation/how-can-i-see-what-destinations-are-used.html
index 900913a94..c2bb8c83e 100644
---
a/output/components/classic/documentation/how-can-i-see-what-destinations-are-used.html
+++
b/output/components/classic/documentation/how-can-i-see-what-destinations-are-used.html
@@ -96,9 +96,9 @@
<p>The easiest way is to use <a href="jmx">JMX</a> by pointing your JMX
console or JConsole at the broker JVM.</p>
-<p>You can also get all of the active destinations from the broker using Java
code via <a
href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/broker/region/Region.html#getDestinations-org.apache.activemq.command.ActiveMQDestination-";>getDestinations()</a>.</p>
+<p>You can also get all of the active destinations from the broker using Java
code via <a
href="http://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/broker/region/Region.html#getDestinations-org.apache.activemq.command.ActiveMQDestination-";>getDestinations()</a>.</p>
-<p>You can also get a Map of all the <a
href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/broker/region/Destination.html";>Destination</a>
objects indexed by ActiveMQDestination via <a
href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/broker/region/Region.html#getDestinationMap--";>getDestinationMap()</a>.
This allows you to look at the individual destination details such as the
queue depths and so forth</p>
+<p>You can also get a Map of all the <a
href="http://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/broker/region/Destination.html";>Destination</a>
objects indexed by ActiveMQDestination via <a
href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/broker/region/Region.html#getDestinationMap--";>getDestinationMap()</a>.
This allows you to look at the individual destination details such as the
queue depths and so forth</p>
</div>
diff --git
a/output/components/classic/documentation/how-do-i-purge-a-queue.html
b/output/components/classic/documentation/how-do-i-purge-a-queue.html
index 07e20d29c..2bb6308a4 100644
--- a/output/components/classic/documentation/how-do-i-purge-a-queue.html
+++ b/output/components/classic/documentation/how-do-i-purge-a-queue.html
@@ -100,9 +100,9 @@
<p>You can use the <a href="web-console">Web Console</a> to view queues,
add/remove queues, purge queues or delete/forward individual messages.</p>
-<p>Another option is to use <a href="jmx">JMX</a> to browse the queues and
call the <strong>purge()</strong> method on the <a
href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/broker/jmx/QueueViewMBean.html";>QueueViewMBean</a>.</p>
+<p>Another option is to use <a href="jmx">JMX</a> to browse the queues and
call the <strong>purge()</strong> method on the <a
href="http://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/broker/jmx/QueueViewMBean.html";>QueueViewMBean</a>.</p>
-<p>You could also delete the queue via removeQueue(String) or
removeTopic(String) methods on the <a
href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/broker/jmx/BrokerViewMBean.html";>BrokerViewMBean</a></p>
+<p>You could also delete the queue via removeQueue(String) or
removeTopic(String) methods on the <a
href="http://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/broker/jmx/BrokerViewMBean.html";>BrokerViewMBean</a></p>
<p>You can also do it <a
href="how-can-i-see-what-destinations-are-used">programmatically</a></p>
diff --git
a/output/components/classic/documentation/how-do-transactions-work.html
b/output/components/classic/documentation/how-do-transactions-work.html
index de93a1a60..ea21612f5 100644
--- a/output/components/classic/documentation/how-do-transactions-work.html
+++ b/output/components/classic/documentation/how-do-transactions-work.html
@@ -98,14 +98,14 @@
<ul>
<li>JMS Transactions - the <code class="language-plaintext
highlighter-rouge">commit()</code>/<code class="language-plaintext
highlighter-rouge">rollback()</code> methods on a Session (which is like doing
<code class="language-plaintext highlighter-rouge">commit()</code>/<code
class="language-plaintext highlighter-rouge">rollback()</code> on a JDBC
connection)</li>
- <li>XA Transactions - where the <a
href="http://activemq.apache.org/maven/apidocs/src-html/org/apache/activemq/ActiveMQXASession.html";>XASession</a>
acts as an <a
href="http://java.sun.com/j2ee/1.4/docs/api/javax/transaction/xa/XAReDevelopers/source";>XAResource</a>
by communicating with the Message Broker, rather like a JDBC Connection takes
place in an XA transaction by communicating with the database.</li>
+ <li>XA Transactions - where the <a
href="http://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/ActiveMQXASession.html";>XASession</a>
acts as an <a
href="http://java.sun.com/j2ee/1.4/docs/api/javax/transaction/xa/XAReDevelopers/source";>XAResource</a>
by communicating with the Message Broker, rather like a JDBC Connection takes
place in an XA transaction by communicating with the database.</li>
</ul>
<p>They are both implemented in a similar manner. When operations are carried
out on a transacted (or XA transacted) session, a transaction command is sent
to the broker, with a unique transaction ID which is then followed by all the
usual commands (send message, acknowledge message etc). When a <code
class="language-plaintext highlighter-rouge">commit()</code> or <code
class="language-plaintext highlighter-rouge">rollback()</code> is called on the
Session, this command is sent to the br [...]
<p>Now the operations carried out on a transacted session inside a
transaction, like a send message or acknowledge message, do not really perform
a real send or acknowledge until the commit occurs. So the Broker explicitly
handles these cases separately - essentially buffering up the commands until
the commit occurs when the messages are really sent or acknowledged.</p>
-<p>ActiveMQ Classic uses <a
href="http://activemq.apache.org/maven/apidocs/src-html/org/apache/activemq/store/TransactionStore.html";>TransactionStore</a>
(implemented by all persistence adapters) to handle transactions. <code
class="language-plaintext highlighter-rouge">TransactionStore</code> will cache
all messages and ACKs until commit or rollback occurs. Besides storing
messages, the broker will withhold dispatching any of the messages until the
session commit. If you wanna see the c [...]
+<p>ActiveMQ Classic uses <a
href="http://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/store/TransactionStore.html";>TransactionStore</a>
(implemented by all persistence adapters) to handle transactions. <code
class="language-plaintext highlighter-rouge">TransactionStore</code> will cache
all messages and ACKs until commit or rollback occurs. Besides storing
messages, the broker will withhold dispatching any of the messages until the
session commit [...]
</div>
diff --git a/output/components/classic/documentation/interceptors.html
b/output/components/classic/documentation/interceptors.html
index 2f5fec409..4080f573e 100644
--- a/output/components/classic/documentation/interceptors.html
+++ b/output/components/classic/documentation/interceptors.html
@@ -109,7 +109,7 @@
<h3 id="how-plugins-work">How plugins work</h3>
-<p>A plugin is an instance of the interface <a
href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/broker/BrokerPlugin.html";>BrokerPlugin</a>
which allows a plugin to add itself into the broker interceptor chain,
typically using the <a
href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/broker/BrokerFilter.html";>BrokerFilter</a>
as a base class to allow only certain operations to be customized.</p>
+<p>A plugin is an instance of the interface <a
href="http://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/broker/BrokerPlugin.html";>BrokerPlugin</a>
which allows a plugin to add itself into the broker interceptor chain,
typically using the <a
href="http://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/broker/BrokerFilter.html";>BrokerFilter</a>
as a base class to allow only certain operations to be customized.</p>
<p>The object that implements the BrokerPlugin interface is called out as a
plugin in the message broker’s XML configuration file (see example below). Your
plugin can then optionally reference other beans that are defined in the XML
file.</p>
<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code><beans
xmlns="http://www.springframework.org/schema/beans";
xmlns:amq="http://activemq.org/config/1.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://www.springframework.org/schema/beans
@@ -169,7 +169,7 @@
http://activemq.apache.org/camel/schema/spring/camel-spring.xsd">
</beans>
</code></pre></div></div>
-<p>At startup, the main or core broker calls your plugin’s installPlugin()
method. This method creates and returns an object that typically extends <a
href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/broker/BrokerFilter.html";>BrokerFilter</a>.</p>
+<p>At startup, the main or core broker calls your plugin’s installPlugin()
method. This method creates and returns an object that typically extends <a
href="http://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/broker/BrokerFilter.html";>BrokerFilter</a>.</p>
<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>import org.apache.activemq.broker.Broker;
import org.apache.activemq.broker.BrokerPlugin;
@@ -181,7 +181,7 @@ public class MyPlugin implements BrokerPlugin {
}
</code></pre></div></div>
-<p>The BrokerFilter class is a convenience class that implements the <a
href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/broker/Broker.html";>Broker</a>
interface. This interface defines all the main operations (e.g.,
addConnection, addSession, etc.) that your implementation can intercept. The
class that extends BrokerFilter overrides any of the methods that are defined
in the Broker interface so that it can intercept the corresponding core
engine’s operations. Here’s an [...]
+<p>The BrokerFilter class is a convenience class that implements the <a
href="http://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/broker/Broker.html";>Broker</a>
interface. This interface defines all the main operations (e.g.,
addConnection, addSession, etc.) that your implementation can intercept. The
class that extends BrokerFilter overrides any of the methods that are defined
in the Broker interface so that it can intercept the corresponding co [...]
<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>import org.apache.activemq.broker.Broker;
import org.apache.activemq.broker.BrokerFilter;
import org.apache.activemq.broker.ConnectionContext;
diff --git a/output/components/classic/documentation/jdbc-support.html
b/output/components/classic/documentation/jdbc-support.html
index 453446ea8..1fada51f6 100644
--- a/output/components/classic/documentation/jdbc-support.html
+++ b/output/components/classic/documentation/jdbc-support.html
@@ -146,7 +146,7 @@
</broker>
</code></pre></div></div>
-<p>For more info on what attributes can be set on the statements element, see
the <a
href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/store/jdbc/Statements.html";>Statements
class</a>. All the settable bean properties can be used as attributes of the
<statements> element.</statements></p>
+<p>For more info on what attributes can be set on the statements element, see
the <a
href="http://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/store/jdbc/Statements.html";>Statements
class</a>. All the settable bean properties can be used as attributes of the
<statements> element.</statements></p>
<h3 id="using-mysql">Using MySQL</h3>
diff --git a/output/components/classic/documentation/jmx.html
b/output/components/classic/documentation/jmx.html
index 4bc46747a..d237a00b3 100644
--- a/output/components/classic/documentation/jmx.html
+++ b/output/components/classic/documentation/jmx.html
@@ -96,7 +96,7 @@
<h2 id="jmx">JMX</h2>
-<p>Apache ActiveMQ Classic has extensive support for JMX to allow you to
monitor and control the behavior of the broker via the <a
href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/broker/jmx/package-summary.html";>JMX
MBeans</a>.</p>
+<p>Apache ActiveMQ Classic has extensive support for JMX to allow you to
monitor and control the behavior of the broker via the <a
href="http://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/broker/jmx/package-summary.html";>JMX
MBeans</a>.</p>
<h3 id="using-jmx-to-monitor-apache-activemq-classic">Using JMX to monitor
Apache ActiveMQ Classic</h3>
diff --git
a/output/components/classic/documentation/multicast-transport-reference.html
b/output/components/classic/documentation/multicast-transport-reference.html
index b45a4fda6..519da1502 100644
--- a/output/components/classic/documentation/multicast-transport-reference.html
+++ b/output/components/classic/documentation/multicast-transport-reference.html
@@ -165,7 +165,7 @@
<h5 id="example-uris">Example URIs</h5>
-<p>To use the default value of “multicast://239.255.2.3:6155” with a default
multicast group name of “default” from <a
href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/transport/discovery/multicast/MulticastDiscoveryAgent.html#DEFAULT_DISCOVERY_URI_STRING";>MulticastDiscoveryAgent</a>
use</p>
+<p>To use the default value of “multicast://239.255.2.3:6155” with a default
multicast group name of “default” from <a
href="http://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/transport/discovery/multicast/MulticastDiscoveryAgent.html#DEFAULT_DISCOVERY_URI_STRING";>MulticastDiscoveryAgent</a>
use</p>
<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>multicast://default
</code></pre></div></div>
<p>To specify the IP address and port use</p>
diff --git a/output/components/classic/documentation/new-features-in-513.html
b/output/components/classic/documentation/new-features-in-513.html
index 094ecb0c0..725f24417 100644
--- a/output/components/classic/documentation/new-features-in-513.html
+++ b/output/components/classic/documentation/new-features-in-513.html
@@ -100,7 +100,7 @@
<li>New transport protocol, <a href="auto">AUTO</a> <a
href="https://issues.apache.org/jira/browse/AMQ-5889";>AMQ-5889</a></li>
<li>Dynamic network support for virtual consumers, <a
href="networks-of-brokers">Networks of Brokers</a> <a
href="https://issues.apache.org/jira/browse/AMQ-6027";>AMQ-6027</a></li>
<li>Pending message size metrics <a
href="https://issues.apache.org/jira/browse/AMQ-5923";>AMQ-5923</a></li>
- <li>New Java API for runtime configuration changes, <a
href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/plugin/java/JavaRuntimeConfigurationBroker.html";>JavaRuntimeConfigurationBroker</a>
to compliment the current <a href="runtime-configuration">runtime
configuration</a> <a
href="https://issues.apache.org/jira/browse/AMQ-5915";>AMQ-5915</a></li>
+ <li>New Java API for runtime configuration changes, <a
href="http://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/plugin/java/JavaRuntimeConfigurationBroker.html";>JavaRuntimeConfigurationBroker</a>
to compliment the current <a href="runtime-configuration">runtime
configuration</a> <a
href="https://issues.apache.org/jira/browse/AMQ-5915";>AMQ-5915</a></li>
<li>Several dependency updates, including Jetty 9.2, Spring 4.1, and Karaf 4
<a href="https://issues.apache.org/jira/browse/AMQ-5957";>AMQ-5957</a></li>
</ul>
diff --git a/output/components/classic/documentation/persistence.html
b/output/components/classic/documentation/persistence.html
index bc1a05294..c0f2cd95d 100644
--- a/output/components/classic/documentation/persistence.html
+++ b/output/components/classic/documentation/persistence.html
@@ -221,7 +221,7 @@ The <a href="amq-message-store">AMQ Message Store</a> which
although faster than
<p>If you don’t want persistence at all you can disable it easily via the <a
href="xml-configuration">Xml Configuration</a>. e.g.</p>
<div class="language-xml highlighter-rouge"><div class="highlight"><pre
class="highlight"><code><span class="nt"><broker</span> <span
class="na">persistent=</span><span class="s">"false"</span><span
class="nt">></span> <span class="nt"></broker></span>
</code></pre></div></div>
-<p>This will make the broker use the
[<memoryPersistenceAdapter>](http://activemq.apache.org/maven/apidocs/org/apache/activemq/store/memory/MemoryPersistenceAdapter.html)
+<p>This will make the broker use the
[<memoryPersistenceAdapter>](http://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/store/memory/MemoryPersistenceAdapter.html)
For an example of using a configuration URI see [How To Unit Test JMS
Code](how-to-unit-test-jms-code)</memoryPersistenceAdapter></p>
diff --git a/output/components/classic/documentation/security.html
b/output/components/classic/documentation/security.html
index f258dd803..4faf1fae5 100644
--- a/output/components/classic/documentation/security.html
+++ b/output/components/classic/documentation/security.html
@@ -539,7 +539,7 @@ In the next step you have to create a new Java class and
let it implement the or
<h2 id="implementing-your-own-custom-security-plugin">Implementing your own
custom Security Plugin</h2>
-<p>All of the various security implementations are implemented as <a
href="interceptors">Interceptors</a> so its very easy to add your own custom
implementation. Its probably easier to start with one of the <a
href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/security/package-summary.html";>simple
implementations</a> though if you are using JAAS you could derive from the <a
href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/jaas/package-summary.html";>JAAS
[...]
+<p>All of the various security implementations are implemented as <a
href="interceptors">Interceptors</a> so its very easy to add your own custom
implementation. Its probably easier to start with one of the <a
href="http://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/security/package-summary.html";>simple
implementations</a> though if you are using JAAS you could derive from the <a
href="http://activemq.apache.org/components/classic/documentation/ [...]
</div>
</div>
diff --git a/output/components/classic/documentation/shiro.html
b/output/components/classic/documentation/shiro.html
index 1bc17451a..cafd76d89 100644
--- a/output/components/classic/documentation/shiro.html
+++ b/output/components/classic/documentation/shiro.html
@@ -387,7 +387,7 @@ broker.setPlugins(new BrokerPlugin[]{shiroPlugin});
<h2 id="design">Design</h2>
-<p>The Shiro plugin is a <a
href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/broker/BrokerPlugin.html";>BrokerPlugin</a>
that inserts 3 <a
href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/broker/BrokerFilter.html";>BrokerFilter</a>s
in the broker filter chain: the <code class="language-plaintext
highlighter-rouge">SubjectFilter</code>, the <code class="language-plaintext
highlighter-rouge">AuthenticationFilter</code> and the <code
class="language-plainte [...]
+<p>The Shiro plugin is a <a
href="http://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/broker/BrokerPlugin.html";>BrokerPlugin</a>
that inserts 3 <a
href="http://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/broker/BrokerFilter.html";>BrokerFilter</a>s
in the broker filter chain: the <code class="language-plaintext
highlighter-rouge">SubjectFilter</code>, the <code class="language-plaintext
highlighter-rouge" [...]
<p><strong>SubjectFilter</strong></p>
@@ -411,7 +411,7 @@ broker.setPlugins(new BrokerPlugin[]{shiroPlugin});
<ul>
<li>the ability to customize exactly how broker clients’ <code
class="language-plaintext highlighter-rouge">Subject</code> instances are
created via a <code class="language-plaintext
highlighter-rouge">ConnectionSubjectFactory</code> and</li>
- <li>the ability to customize how the ActiveMQ Classic ConnectionContext’s <a
href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/security/SecurityContext.html";>SecurityContext</a>
is constructed.</li>
+ <li>the ability to customize how the ActiveMQ Classic ConnectionContext’s <a
href="http://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/security/SecurityContext.html";>SecurityContext</a>
is constructed.</li>
</ul>
<p>Unless you’re deeply familiar with ActiveMQ Classic’s security model, you
can safely skip to <strong>Authentication</strong> below.</p>
diff --git a/output/components/classic/documentation/uri-protocols.html
b/output/components/classic/documentation/uri-protocols.html
index 059538f43..e22cc81c9 100644
--- a/output/components/classic/documentation/uri-protocols.html
+++ b/output/components/classic/documentation/uri-protocols.html
@@ -96,7 +96,7 @@
<p>ActiveMQ Classic is designed to support mutliple different <a
href="topologies">topologies</a> and protocols. Which one you use depends on
your messaging requirements, quality of service and network topology.</p>
-<p>The following table describes the different network protocols available for
JMS clients along with showing the connection URL string you use to enable this
communication protocol. On the broker side there are additional <a
href="configuring-transports">transports</a> supported. You can specify the
connection URL on an <a
href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/ActiveMQConnectionFactory.html";>ActiveMQConnectionFactory</a>
(in a constructor or via the brokerUR [...]
+<p>The following table describes the different network protocols available for
JMS clients along with showing the connection URL string you use to enable this
communication protocol. On the broker side there are additional <a
href="configuring-transports">transports</a> supported. You can specify the
connection URL on an <a
href="http://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/ActiveMQConnectionFactory.html";>ActiveMQConnectionFactory</a>
(in [...]
<p>e.g. if you don’t want to bother setting up JNDI and so forth and just
wanna create a JMS connection you can do something like</p>
@@ -180,7 +180,7 @@ Connection connection = factory.createConnection();</p>
<p>The <em>Server</em> column above indicates whether a protocol can be used
in an ActiveMQ Classic broker transport connector. All of the above protocols
can be used in a JMS client to connect to the messaging fabric; only those
protocols indicated can be used in a broker-side transport connector.</p>
-<p>When connecting to an ActiveMQ Classic broker, this could reside locally
inside your JVM or be remote on another machine somewhere. If you want to
enable the deployment of the ActiveMQ Classic inside your JVM you can enable
the useEmbeddedBroker property on the <a
href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/ActiveMQConnectionFactory.html";>ActiveMQConnectionFactory</a>.</p>
+<p>When connecting to an ActiveMQ Classic broker, this could reside locally
inside your JVM or be remote on another machine somewhere. If you want to
enable the deployment of the ActiveMQ Classic inside your JVM you can enable
the useEmbeddedBroker property on the <a
href="http://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/ActiveMQConnectionFactory.html";>ActiveMQConnectionFactory</a>.</p>
<p>Please refer to the <a href="topologies">topologies overview</a> to see how
we can use ActiveMQ Classic in many different topologies to suit your messaging
needs.</p>
diff --git
a/output/components/classic/documentation/what-is-the-prefetch-limit-for.html
b/output/components/classic/documentation/what-is-the-prefetch-limit-for.html
index bc53093b8..8948e9f44 100644
---
a/output/components/classic/documentation/what-is-the-prefetch-limit-for.html
+++
b/output/components/classic/documentation/what-is-the-prefetch-limit-for.html
@@ -114,7 +114,7 @@
<h3 id="specifying-the-prefetchpolicy">Specifying the PrefetchPolicy</h3>
-<p>You can specify an instance of the <a
href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/ActiveMQPrefetchPolicy.html";>ActiveMQPrefetchPolicy</a>
on an <a
href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/ActiveMQConnectionFactory.html";>ActiveMQConnectionFactory</a>
or <a
href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/ActiveMQConnection.html";>ActiveMQConnection</a>.
This allows you to configure all the individual prefetch values; as [...]
+<p>You can specify an instance of the <a
href="http://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/ActiveMQPrefetchPolicy.html";>ActiveMQPrefetchPolicy</a>
on an <a
href="http://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/ActiveMQConnectionFactory.html";>ActiveMQConnectionFactory</a>
or <a
href="http://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/ActiveMQConnection
[...]
<ul>
<li>
@@ -143,7 +143,7 @@ consumer = session.createConsumer(queue);
</code></pre></div></div>
<h3 id="pooled-consumers-and-prefetch">Pooled Consumers and Prefetch</h3>
-<p>Consuming messages from a pool of consumers an be problematic due to
prefetch. Unconsumed prefetched messages are only released when a consumer is
closed, but with a pooled consumer the close is deferred (for reuse) till the
consumer pool closes. This leaves prefetched messages unconsumed till the
consumer is reused. This feature can be desirable from a performance
perspective. However, it can lead to out-of-order message delivery when there
is more than one consumer in the pool. For [...]
+<p>Consuming messages from a pool of consumers an be problematic due to
prefetch. Unconsumed prefetched messages are only released when a consumer is
closed, but with a pooled consumer the close is deferred (for reuse) till the
consumer pool closes. This leaves prefetched messages unconsumed till the
consumer is reused. This feature can be desirable from a performance
perspective. However, it can lead to out-of-order message delivery when there
is more than one consumer in the pool. For [...]
<p>Pooling consumers is supported by Springs CachingConnectionFactory
(although turned off by default). In case you use the CachingConnectionFactory
with multiple consumer threads configured in Springs
DefaultMessageListenerContainer (DMLC) then you either want to turn off
consumer pooling in the CachingConnectionFactory (its off by default) or you
may want to use a prefetch of 0 when pooling consumers. In this way, the
consumer will poll for messages on each call to <code class="languag [...]
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@activemq.apache.org
For additional commands, e-mail: commits-h...@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
