This is an automated email from the ASF dual-hosted git repository.
jbertram pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/activemq-website.git
The following commit(s) were added to refs/heads/main by this push:
new d3f4485 Fix various broken links
d3f4485 is described below
commit d3f4485836a2622ff9ec941b7123e25fc5e2eb3e
Author: Justin Bertram <[email protected]>
AuthorDate: Mon Dec 20 11:19:15 2021 -0600
Fix various broken links
---
src/40-rc-1-guide.md | 1 -
src/integrating-apache-activemq-with-jboss.md | 10 +--
src/jboss-integration.md | 10 +--
src/release-info.md | 1 -
...ivemq-is-there-a-way-to-measure-its-progress.md | 5 +-
src/xbean-xml-reference-41.md | 8 +-
src/xbean-xml-reference-50.md | 90 +++++++++++-----------
7 files changed, 60 insertions(+), 65 deletions(-)
diff --git a/src/40-rc-1-guide.md b/src/40-rc-1-guide.md
index 0c7cb1f..d135a96 100644
--- a/src/40-rc-1-guide.md
+++ b/src/40-rc-1-guide.md
@@ -14,7 +14,6 @@ ActiveMQ 4.0-RC-1 Release Guide
General Release Information
---------------------------
-* [Current
RoadMap](http://jira.activemq.org/jira/browse/AMQ?report=com.atlassian.jira.plugin.system.project:roadmap-panel)
* [Release Guide](release-guide)
* [Signing Releases](http://wiki.apache.org/incubator/SigningReleases)
* [Apache Mirror Guidelines](http://apache.org/dev/mirrors.html)
diff --git a/src/integrating-apache-activemq-with-jboss.md
b/src/integrating-apache-activemq-with-jboss.md
index c1a724e..9269399 100644
--- a/src/integrating-apache-activemq-with-jboss.md
+++ b/src/integrating-apache-activemq-with-jboss.md
@@ -11,9 +11,9 @@ type: activemq5
Integrating Apache ActiveMQ with JBoss
======================================
-Integration with application servers is a common scenario in the enterprise
Java world, especially when it comes to messaging.
[ActiveMQ](http://activemq.org/) is a JMS 1.1 compliant, open source, Apache
Licensed, message oriented middleware (MOM) with
[many](http://activemq.org/siteFeatures/New FeaturesFeatures/New
Features/Features/New Features/changes-in-40),
[many](http://activemq.org/siteFeatures/New Features/new-features-in-41)
features far beyond the JMS specification. ActiveMQ of [...]
+Integration with application servers is a common scenario in the enterprise
Java world, especially when it comes to messaging. ActiveMQ is a JMS 1.1
compliant, open source, Apache Licensed, message oriented middleware (MOM) with
[many](changes-in-40), [many](new-features-in-41) features far beyond the JMS
specification. ActiveMQ offers many different [points of
connectivity](connectivity), many [cross language
clients](cross-language-clients) and many [pluggable transport protocols](prot
[...]
-One of the application servers in the open source world is JBoss. A very
common requirement is to configure ActiveMQ as the messaging infrastructure
within JBoss. Although there is [a bit of
documentation](http://www.activemq.org/siteConnectivity/ContainersConnectivity/Containers/Connectivity/Containers/jboss-integration)
on this integration, this article seeks to provide much more detail and
explanation. So if you have a need to integrate ActiveMQ with JBoss, this
article is for you.
+One of the application servers in the open source world is JBoss. A very
common requirement is to configure ActiveMQ as the messaging infrastructure
within JBoss. Although there is [a bit of documentation](jboss-integration) on
this integration, this article seeks to provide much more detail and
explanation. So if you have a need to integrate ActiveMQ with JBoss, this
article is for you.
This article explains how to configure JBoss to start up ActiveMQ as part of
its lifecycle and how to configure the ActiveMQ resource adapter to handle the
messaging and transactionality between ActiveMQ and JBoss.
@@ -22,7 +22,7 @@ Requirements
Below are the software requirements for this article with links to download
each:
-* [Apache ActiveMQ
4.0.1+](http://activemq.org/siteOverviewOverview/Overview/download)
+* [Apache ActiveMQ 4.0.1+](download)
* [JBoss
4.0.4+](http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=16942&release_id=416591)
* [Sun Java 1.5+](http://www.java.com/en/download/index.jsp)
* [Apache Ant 1.6+](http://ant.apache.org/bindownload.cgi)
@@ -334,9 +334,9 @@ The `<persistenceAdapter>` element should be reconfigured
to store its data in a
```
Now, modify the `dataDirectory` attribute of the `journaledJDBC` element to be
the following: `${jboss.server.data.dir}/activemq`.
-The `<transportConnectors>` element is used to advertise the ActiveMQ broker
for client-to-broker communications and the `<networkConnectors>` element
advertises the ActiveMQ broker for broker-to-broker communications. The default
configuration is to use the ActiveMQ [multicast
transport](http://www.activemq.org/siteUsing ActiveMQ/Configuring
Transports/ActiveMQ Connection URIs/multicast-transport-reference) for both.
This is simply an easy configuration under which to get ActiveMQ up an [...]
+The `<transportConnectors>` element is used to advertise the ActiveMQ broker
for client-to-broker communications and the `<networkConnectors>` element
advertises the ActiveMQ broker for broker-to-broker communications. The default
configuration is to use the ActiveMQ [multicast
transport](multicast-transport-reference) for both. This is simply an easy
configuration under which to get ActiveMQ up and running, so we'll just leave
it at that for the time being.
-`_NOTE:_** There are far more configuration options available for ActiveMQ
than are noted here. The configuration above is only enough to just get
ActiveMQ up and running, nothing more. For more information on the ActiveMQ
configuration, see the [ActiveMQ 4.1 XML
Reference](http://www.activemq.org/siteUsing ActiveMQ/Xml ReferenceUsing
ActiveMQ/Xml Reference/Using ActiveMQ/Xml Reference/xbean-xml-reference-41).
+`_NOTE:_** There are far more configuration options available for ActiveMQ
than are noted here. The configuration above is only enough to just get
ActiveMQ up and running, nothing more. For more information on the ActiveMQ
configuration, see the [ActiveMQ 4.1 XML Reference](xbean-xml-reference-41).
Now we just need to start up JBoss to assure that it comes up correctly
without error using the same commands we used previously to start JBoss:
```
diff --git a/src/jboss-integration.md b/src/jboss-integration.md
index c1a724e..9269399 100644
--- a/src/jboss-integration.md
+++ b/src/jboss-integration.md
@@ -11,9 +11,9 @@ type: activemq5
Integrating Apache ActiveMQ with JBoss
======================================
-Integration with application servers is a common scenario in the enterprise
Java world, especially when it comes to messaging.
[ActiveMQ](http://activemq.org/) is a JMS 1.1 compliant, open source, Apache
Licensed, message oriented middleware (MOM) with
[many](http://activemq.org/siteFeatures/New FeaturesFeatures/New
Features/Features/New Features/changes-in-40),
[many](http://activemq.org/siteFeatures/New Features/new-features-in-41)
features far beyond the JMS specification. ActiveMQ of [...]
+Integration with application servers is a common scenario in the enterprise
Java world, especially when it comes to messaging. ActiveMQ is a JMS 1.1
compliant, open source, Apache Licensed, message oriented middleware (MOM) with
[many](changes-in-40), [many](new-features-in-41) features far beyond the JMS
specification. ActiveMQ offers many different [points of
connectivity](connectivity), many [cross language
clients](cross-language-clients) and many [pluggable transport protocols](prot
[...]
-One of the application servers in the open source world is JBoss. A very
common requirement is to configure ActiveMQ as the messaging infrastructure
within JBoss. Although there is [a bit of
documentation](http://www.activemq.org/siteConnectivity/ContainersConnectivity/Containers/Connectivity/Containers/jboss-integration)
on this integration, this article seeks to provide much more detail and
explanation. So if you have a need to integrate ActiveMQ with JBoss, this
article is for you.
+One of the application servers in the open source world is JBoss. A very
common requirement is to configure ActiveMQ as the messaging infrastructure
within JBoss. Although there is [a bit of documentation](jboss-integration) on
this integration, this article seeks to provide much more detail and
explanation. So if you have a need to integrate ActiveMQ with JBoss, this
article is for you.
This article explains how to configure JBoss to start up ActiveMQ as part of
its lifecycle and how to configure the ActiveMQ resource adapter to handle the
messaging and transactionality between ActiveMQ and JBoss.
@@ -22,7 +22,7 @@ Requirements
Below are the software requirements for this article with links to download
each:
-* [Apache ActiveMQ
4.0.1+](http://activemq.org/siteOverviewOverview/Overview/download)
+* [Apache ActiveMQ 4.0.1+](download)
* [JBoss
4.0.4+](http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=16942&release_id=416591)
* [Sun Java 1.5+](http://www.java.com/en/download/index.jsp)
* [Apache Ant 1.6+](http://ant.apache.org/bindownload.cgi)
@@ -334,9 +334,9 @@ The `<persistenceAdapter>` element should be reconfigured
to store its data in a
```
Now, modify the `dataDirectory` attribute of the `journaledJDBC` element to be
the following: `${jboss.server.data.dir}/activemq`.
-The `<transportConnectors>` element is used to advertise the ActiveMQ broker
for client-to-broker communications and the `<networkConnectors>` element
advertises the ActiveMQ broker for broker-to-broker communications. The default
configuration is to use the ActiveMQ [multicast
transport](http://www.activemq.org/siteUsing ActiveMQ/Configuring
Transports/ActiveMQ Connection URIs/multicast-transport-reference) for both.
This is simply an easy configuration under which to get ActiveMQ up an [...]
+The `<transportConnectors>` element is used to advertise the ActiveMQ broker
for client-to-broker communications and the `<networkConnectors>` element
advertises the ActiveMQ broker for broker-to-broker communications. The default
configuration is to use the ActiveMQ [multicast
transport](multicast-transport-reference) for both. This is simply an easy
configuration under which to get ActiveMQ up and running, so we'll just leave
it at that for the time being.
-`_NOTE:_** There are far more configuration options available for ActiveMQ
than are noted here. The configuration above is only enough to just get
ActiveMQ up and running, nothing more. For more information on the ActiveMQ
configuration, see the [ActiveMQ 4.1 XML
Reference](http://www.activemq.org/siteUsing ActiveMQ/Xml ReferenceUsing
ActiveMQ/Xml Reference/Using ActiveMQ/Xml Reference/xbean-xml-reference-41).
+`_NOTE:_** There are far more configuration options available for ActiveMQ
than are noted here. The configuration above is only enough to just get
ActiveMQ up and running, nothing more. For more information on the ActiveMQ
configuration, see the [ActiveMQ 4.1 XML Reference](xbean-xml-reference-41).
Now we just need to start up JBoss to assure that it comes up correctly
without error using the same commands we used previously to start JBoss:
```
diff --git a/src/release-info.md b/src/release-info.md
index 6a92e0d..bb123eb 100644
--- a/src/release-info.md
+++ b/src/release-info.md
@@ -11,7 +11,6 @@ type: activemq5
General Release Information
---------------------------
-* [Current
RoadMap](http://jira.activemq.org/jira/browse/AMQ?report=com.atlassian.jira.plugin.system.project:roadmap-panel)
* [Release Guide](release-guide)
* [Signing Releases](http://wiki.apache.org/incubator/SigningReleases)
* [Apache Mirror Guidelines](http://apache.org/dev/mirrors.html)
diff --git
a/src/while-posting-large-binary-file-to-activemq-is-there-a-way-to-measure-its-progress.md
b/src/while-posting-large-binary-file-to-activemq-is-there-a-way-to-measure-its-progress.md
index 6472e31..2113a38 100644
---
a/src/while-posting-large-binary-file-to-activemq-is-there-a-way-to-measure-its-progress.md
+++
b/src/while-posting-large-binary-file-to-activemq-is-there-a-way-to-measure-its-progress.md
@@ -8,8 +8,5 @@ type: activemq5
[FAQ](faq) > [Using Apache ActiveMQ](using-apache-activemq) > [While posting
large binary file to activeMQ, is there a way to measure its
progress](while-posting-large-binary-file-to-activemq-is-there-a-way-to-measure-its-progress)
-If you are using the JMS Streams feature with 4.x of ActiveMQ
-[http://activemq.org/JMS+Streams](http://activemq.org/JMS+Streams)
-
-you'd be able to watch the progress in a JMX console or HermesJMS by looking
at the queue depths; each large 1Gb file is split into individual JMS messages
so you can monitor queue depth etc to track progress
+If you are using the [JMS Streams](jms-streams) feature with 4.x of ActiveMQ
you'd be able to watch the progress in a JMX console or HermesJMS by looking at
the queue depths; each large 1Gb file is split into individual JMS messages so
you can monitor queue depth etc to track progress
diff --git a/src/xbean-xml-reference-41.md b/src/xbean-xml-reference-41.md
index c6f2aba..86f895c 100644
--- a/src/xbean-xml-reference-41.md
+++ b/src/xbean-xml-reference-41.md
@@ -105,7 +105,7 @@ Represents a virtual topic which forwards to a number of
other destinations.
_\<virtualTopic>_
-Creates [Virtual Topics](http://activemq.org/siteFeatures/Destination
Features/Features/Destination Features/virtual-destinations) using a prefix and
postfix. The virtual destination creates a wildcard that is then used to look
up all active queue subscriptions which match.
+Creates [Virtual Topics](virtual-destinations) using a prefix and postfix. The
virtual destination creates a wildcard that is then used to look up all active
queue subscriptions which match.
#### The _org.apache.activemq.broker.region.policy.PolicyMap_ Type
Implementations
@@ -2888,7 +2888,7 @@ virtualDestinations
### The _\<virtualTopic>_ Element
-Creates [Virtual Topics](http://activemq.org/siteFeatures/Destination
Features/Features/Destination Features/virtual-destinations) using a prefix and
postfix. The virtual destination creates a wildcard that is then used to look
up all active queue subscriptions which match.
+Creates [Virtual Topics](virtual-destinations) using a prefix and postfix. The
virtual destination creates a wildcard that is then used to look up all active
queue subscriptions which match.
#### Properties
@@ -3183,9 +3183,9 @@ Used to keep track of how much of something is being used
so that a productive w
_\<virtualDestinationInterceptor>_
-Implements [Virtual
Topics](http://incubator.apache.org/activemqFeatures/Destination
Features/Features/Destination Features/virtual-destinations).
+Implements [Virtual Topics](virtual-destinations).
_\<virtualTopic>_
-Creates [Virtual Topics](http://activemq.org/siteFeatures/Destination
Features/Features/Destination Features/virtual-destinations) using a prefix and
postfix. The virtual destination creates a wildcard that is then used to look
up all active queue subscriptions which match.
+Creates [Virtual Topics](virtual-destinations) using a prefix and postfix. The
virtual destination creates a wildcard that is then used to look up all active
queue subscriptions which match.
diff --git a/src/xbean-xml-reference-50.md b/src/xbean-xml-reference-50.md
index 6a9413c..d01d4fd 100644
--- a/src/xbean-xml-reference-50.md
+++ b/src/xbean-xml-reference-50.md
@@ -175,11 +175,11 @@ Pending messages
_\<connectionFactory>_
-A [Spring](http://www.springframework.org/) enhanced connection factory which
will automatically use the Spring bean name as the clientIDPrefix property so
that connections created have client IDs related to your Spring.xml file for
easier comprehension from [JMX](http://activemq.apache.orgFeatures/jmx).
+A [Spring](http://www.springframework.org/) enhanced connection factory which
will automatically use the Spring bean name as the clientIDPrefix property so
that connections created have client IDs related to your Spring.xml file for
easier comprehension from [JMX](jmx).
_\<xaConnectionFactory>_
-A [Spring](http://www.springframework.org/) enhanced XA connection factory
which will automatically use the Spring bean name as the clientIDPrefix
property so that connections created have client IDs related to your Spring.xml
file for easier comprehension from
[JMX](http://activemq.apache.orgFeatures/jmx).
+A [Spring](http://www.springframework.org/) enhanced XA connection factory
which will automatically use the Spring bean name as the clientIDPrefix
property so that connections created have client IDs related to your Spring.xml
file for easier comprehension from [JMX](jmx).
#### The _org.apache.activemq.broker.region.virtual.VirtualDestination_ Type
Implementations
@@ -193,7 +193,7 @@ Represents a virtual topic which forwards to a number of
other destinations.
_\<virtualTopic>_
-Creates [Virtual Topics](http://activemq.org/siteFeatures/Destination
Features/Features/Destination Features/virtual-destinations) using a prefix and
postfix. The virtual destination creates a wildcard that is then used to look
up all active queue subscriptions which match.
+Creates [Virtual Topics](virtual-destinations) using a prefix and postfix. The
virtual destination creates a wildcard that is then used to look up all active
queue subscriptions which match.
#### The _org.apache.activemq.broker.region.policy.PolicyMap_ Type
Implementations
@@ -267,11 +267,11 @@ This implementation of {@link SubscriptionRecoveryPolicy}
will keep a timed buff
_\<connectionFactory>_
-A [Spring](http://www.springframework.org/) enhanced connection factory which
will automatically use the Spring bean name as the clientIDPrefix property so
that connections created have client IDs related to your Spring.xml file for
easier comprehension from [JMX](http://activemq.apache.orgFeatures/jmx).
+A [Spring](http://www.springframework.org/) enhanced connection factory which
will automatically use the Spring bean name as the clientIDPrefix property so
that connections created have client IDs related to your Spring.xml file for
easier comprehension from [JMX](jmx).
_\<xaConnectionFactory>_
-A [Spring](http://www.springframework.org/) enhanced XA connection factory
which will automatically use the Spring bean name as the clientIDPrefix
property so that connections created have client IDs related to your Spring.xml
file for easier comprehension from
[JMX](http://activemq.apache.orgFeatures/jmx).
+A [Spring](http://www.springframework.org/) enhanced XA connection factory
which will automatically use the Spring bean name as the clientIDPrefix
property so that connections created have client IDs related to your Spring.xml
file for easier comprehension from [JMX](jmx).
#### The _org.apache.activemq.broker.jmx.ManagementContext_ Type
Implementations
@@ -321,11 +321,11 @@ Pending
_\<messageGroupHashBucketFactory>_
-A factory to create instances of {@link SimpleMessageGroupMap} when
implementing the [Message Groups](http://activemq.apache.org/Features/Consumer
Features/message-groups) functionality.
+A factory to create instances of {@link SimpleMessageGroupMap} when
implementing the [Message Groups](message-groups) functionality.
_\<simpleMessageGroupMapFactory>_
-A factory to create instances of {@link SimpleMessageGroupMap} when
implementing the [Message Groups](http://activemq.apache.org/Features/Consumer
Features/message-groups) functionality.
+A factory to create instances of {@link SimpleMessageGroupMap} when
implementing the [Message Groups](message-groups) functionality.
#### The _org.apache.activemq.usage.StoreUsage_ Type Implementations
@@ -489,11 +489,11 @@ Dispatch policy that causes every subscription to see
messages in the same order
_\<connectionFactory>_
-A [Spring](http://www.springframework.org/) enhanced connection factory which
will automatically use the Spring bean name as the clientIDPrefix property so
that connections created have client IDs related to your Spring.xml file for
easier comprehension from [JMX](http://activemq.apache.orgFeatures/jmx).
+A [Spring](http://www.springframework.org/) enhanced connection factory which
will automatically use the Spring bean name as the clientIDPrefix property so
that connections created have client IDs related to your Spring.xml file for
easier comprehension from [JMX](jmx).
_\<xaConnectionFactory>_
-A [Spring](http://www.springframework.org/) enhanced XA connection factory
which will automatically use the Spring bean name as the clientIDPrefix
property so that connections created have client IDs related to your Spring.xml
file for easier comprehension from
[JMX](http://activemq.apache.orgFeatures/jmx).
+A [Spring](http://www.springframework.org/) enhanced XA connection factory
which will automatically use the Spring bean name as the clientIDPrefix
property so that connections created have client IDs related to your Spring.xml
file for easier comprehension from [JMX](jmx).
#### The _javax.jms.Queue_ Type Implementations
@@ -551,7 +551,7 @@ A Flow provides different dispatch policies within the NMR
_\<masterConnector>_
-Connects a Slave Broker to a Master when using [Master
Slave](http://activemq.apache.orgFeatures/ClusteringFeatures/Clustering/Features/Clustering/masterslave)
for High Availability of messages.
+Connects a Slave Broker to a Master when using [Master Slave](masterslave) for
High Availability of messages.
_\<memoryUsage>_
@@ -603,11 +603,11 @@ Create an Outbound Topic Bridge
_\<mirroredQueue>_
-Creates [Mirrored Queue](http://activemq.org/siteFeatures/Destination
FeaturesFeatures/Destination Features/Features/Destination
Features/mirrored-queues) using a prefix and postfix to define the topic name
on which to mirror the queue to.
+Creates [Mirrored Queue](mirrored-queues) using a prefix and postfix to define
the topic name on which to mirror the queue to.
_\<virtualDestinationInterceptor>_
-Implements [Virtual Topics](http://activemq.apache.orgFeatures/Destination
Features/Features/Destination Features/virtual-destinations).
+Implements [Virtual Topics](virtual-destinations).
#### The _org.apache.activemq.filter.DestinationMap_ Type Implementations
@@ -1189,7 +1189,7 @@ useMirroredQueues
_boolean_
-Sets whether or not [Mirrored
Queues](http://activemq.apache.orgFeatures/Destination
FeaturesFeatures/Destination Features/Features/Destination
Features/mirrored-queues) should be supported by default if they have not been
explicitly configured.
+Sets whether or not [Mirrored Queues](mirrored-queues) should be supported by
default if they have not been explicitly configured.
useShutdownHook
@@ -1201,7 +1201,7 @@ useVirtualTopics
_boolean_
-Sets whether or not [Virtual
Topics](http://activemq.apache.orgFeatures/Destination
Features/Features/Destination Features/virtual-destinations) should be
supported by default if they have not been explicitly configured.
+Sets whether or not [Virtual Topics](virtual-destinations) should be supported
by default if they have not been explicitly configured.
vmConnectorURI
@@ -1399,7 +1399,7 @@ Sets the destination file name to create the destination
diagram
### The _\<connectionFactory>_ Element
-A [Spring](http://www.springframework.org/) enhanced connection factory which
will automatically use the Spring bean name as the clientIDPrefix property so
that connections created have client IDs related to your Spring.xml file for
easier comprehension from [JMX](http://activemq.apache.orgFeatures/jmx).
+A [Spring](http://www.springframework.org/) enhanced connection factory which
will automatically use the Spring bean name as the clientIDPrefix property so
that connections created have client IDs related to your Spring.xml file for
easier comprehension from [JMX](jmx).
#### Properties
@@ -1435,7 +1435,7 @@ brokerURL
_java.lang.String_
-Sets the [connection URL](http://activemq.apache.orgUsing
ActiveMQ/configuring-transports) used to connect to the ActiveMQ broker.
+Sets the [connection URL](configuring-transports) used to connect to the
ActiveMQ broker.
clientID
@@ -1475,19 +1475,19 @@ dispatchAsync
_boolean_
-Enables or disables the default setting of whether or not consumers have their
messages [dispatched synchronously or asynchronously by the
broker](http://activemq.apache.org/Features/Consumer
Features/consumer-dispatch-async). For non-durable topics for example we
typically dispatch synchronously by default to minimize context switches which
boost performance. However sometimes its better to go slower to ensure that a
single blocked consumer socket does not block delivery to other consumers.
+Enables or disables the default setting of whether or not consumers have their
messages [dispatched synchronously or asynchronously by the
broker](consumer-dispatch-async). For non-durable topics for example we
typically dispatch synchronously by default to minimize context switches which
boost performance. However sometimes its better to go slower to ensure that a
single blocked consumer socket does not block delivery to other consumers.
exclusiveConsumer
_boolean_
-Enables or disables whether or not queue consumers should be exclusive or not
for example to preserve ordering when not using [Message
Groups](http://activemq.apache.org/Features/Consumer Features/message-groups)
+Enables or disables whether or not queue consumers should be exclusive or not
for example to preserve ordering when not using [Message Groups](message-groups)
nestedMapAndListEnabled
_boolean_
-Enables/disables whether or not Message properties and MapMessage entries
support [Nested Structures](http://activemq.apache.orgFeatures/Message
Features/structured-message-properties-and-mapmessages) of Map and List objects
+Enables/disables whether or not Message properties and MapMessage entries
support [Nested Structures](structured-message-properties-and-mapmessages) of
Map and List objects
objectMessageSerializationDefered
@@ -1515,7 +1515,7 @@ prefetchPolicy
_org.apache.activemq.ActiveMQPrefetchPolicy_
-Sets the [prefetch policy](http://activemq.apache.orgCommunity/FAQ/Using
Apache ActiveMQCommunity/FAQ/Using Apache ActiveMQ/Community/FAQ/Using Apache
ActiveMQ/what-is-the-prefetch-limit-for) for consumers created by this
connection.
+Sets the [prefetch policy](what-is-the-prefetch-limit-for) for consumers
created by this connection.
producerWindowSize
@@ -1553,7 +1553,7 @@ useAsyncSend
_boolean_
-Forces the use of [Async Sends](http://activemq.apache.orgFeatures/Message
Dispatching Features/async-sends) which adds a massive performance boost; but
means that the send() method will return immediately whether the message has
been sent or not which could lead to message loss.
+Forces the use of [Async Sends](async-sends) which adds a massive performance
boost; but means that the send() method will return immediately whether the
message has been sent or not which could lead to message loss.
useBeanNameAsClientIdPrefix
@@ -1581,7 +1581,7 @@ warnAboutUnstartedConnectionTimeout
_long_
-Enables the timeout from a connection creation to when a warning is generated
if the connection is not properly started via {@link Connection#start()} and a
message is received by a consumer. It is a very common gotcha to forget to
[start the
connection](http://activemq.apache.orgCommunity/FAQ/ErrorsCommunity/FAQ/Errors/Community/FAQ/Errors/i-am-not-receiving-any-messages-what-is-wrong)
so this option makes the default case to create a warning if the user forgets.
To disable the warning [...]
+Enables the timeout from a connection creation to when a warning is generated
if the connection is not properly started via {@link Connection#start()} and a
message is received by a consumer. It is a very common gotcha to forget to
[start the connection](i-am-not-receiving-any-messages-what-is-wrong) so this
option makes the default case to create a warning if the user forgets. To
disable the warning just set the value to < 0 (say -1).
watchTopicAdvisories
@@ -2922,7 +2922,7 @@ _boolean_
### The _\<masterConnector>_ Element
-Connects a Slave Broker to a Master when using [Master
Slave](http://activemq.apache.orgFeatures/ClusteringFeatures/Clustering/Features/Clustering/masterslave)
for High Availability of messages.
+Connects a Slave Broker to a Master when using [Master Slave](masterslave) for
High Availability of messages.
#### Properties
@@ -3040,7 +3040,7 @@ _float_
### The _\<messageGroupHashBucketFactory>_ Element
-A factory to create instances of {@link SimpleMessageGroupMap} when
implementing the [Message Groups](http://activemq.apache.org/Features/Consumer
Features/message-groups) functionality.
+A factory to create instances of {@link SimpleMessageGroupMap} when
implementing the [Message Groups](message-groups) functionality.
#### Properties
@@ -3058,7 +3058,7 @@ Sets the number of hash buckets to use for the message
group functionality. This
### The _\<mirroredQueue>_ Element
-Creates [Mirrored Queue](http://activemq.org/siteFeatures/Destination
FeaturesFeatures/Destination Features/Features/Destination
Features/mirrored-queues) using a prefix and postfix to define the topic name
on which to mirror the queue to.
+Creates [Mirrored Queue](mirrored-queues) using a prefix and postfix to define
the topic name on which to mirror the queue to.
#### Properties
@@ -3616,7 +3616,7 @@ messageGroupMapFactory
_org.apache.activemq.broker.region.group.MessageGroupMapFactory_
-Sets the factory used to create new instances of {MessageGroupMap} used to
implement the [Message Groups](http://activemq.apache.org/Features/Consumer
Features/message-groups) functionality.
+Sets the factory used to create new instances of {MessageGroupMap} used to
implement the [Message Groups](message-groups) functionality.
optimizedDispatch
@@ -3980,7 +3980,7 @@ _javax.jms.Connection_
### The _\<simpleMessageGroupMapFactory>_ Element
-A factory to create instances of {@link SimpleMessageGroupMap} when
implementing the [Message Groups](http://activemq.apache.org/Features/Consumer
Features/message-groups) functionality.
+A factory to create instances of {@link SimpleMessageGroupMap} when
implementing the [Message Groups](message-groups) functionality.
### The _\<statements>_ Element
@@ -4594,7 +4594,7 @@ _long_
### The _\<virtualDestinationInterceptor>_ Element
-Implements [Virtual Topics](http://activemq.apache.orgFeatures/Destination
Features/Features/Destination Features/virtual-destinations).
+Implements [Virtual Topics](virtual-destinations).
#### Properties
@@ -4610,7 +4610,7 @@ virtualDestinations
### The _\<virtualTopic>_ Element
-Creates [Virtual Topics](http://activemq.org/siteFeatures/Destination
Features/Features/Destination Features/virtual-destinations) using a prefix and
postfix. The virtual destination creates a wildcard that is then used to look
up all active queue subscriptions which match.
+Creates [Virtual Topics](virtual-destinations) using a prefix and postfix. The
virtual destination creates a wildcard that is then used to look up all active
queue subscriptions which match.
#### Properties
@@ -4650,7 +4650,7 @@ Pending messages
### The _\<xaConnectionFactory>_ Element
-A [Spring](http://www.springframework.org/) enhanced XA connection factory
which will automatically use the Spring bean name as the clientIDPrefix
property so that connections created have client IDs related to your Spring.xml
file for easier comprehension from
[JMX](http://activemq.apache.orgFeatures/jmx).
+A [Spring](http://www.springframework.org/) enhanced XA connection factory
which will automatically use the Spring bean name as the clientIDPrefix
property so that connections created have client IDs related to your Spring.xml
file for easier comprehension from [JMX](jmx).
#### Properties
@@ -4686,7 +4686,7 @@ brokerURL
_java.lang.String_
-Sets the [connection URL](http://activemq.apache.orgUsing
ActiveMQ/configuring-transports) used to connect to the ActiveMQ broker.
+Sets the [connection URL](configuring-transports) used to connect to the
ActiveMQ broker.
clientID
@@ -4726,19 +4726,19 @@ dispatchAsync
_boolean_
-Enables or disables the default setting of whether or not consumers have their
messages [dispatched synchronously or asynchronously by the
broker](http://activemq.apache.org/Features/Consumer
Features/consumer-dispatch-async). For non-durable topics for example we
typically dispatch synchronously by default to minimize context switches which
boost performance. However sometimes its better to go slower to ensure that a
single blocked consumer socket does not block delivery to other consumers.
+Enables or disables the default setting of whether or not consumers have their
messages [dispatched synchronously or asynchronously by the
broker](consumer-dispatch-async). For non-durable topics for example we
typically dispatch synchronously by default to minimize context switches which
boost performance. However sometimes its better to go slower to ensure that a
single blocked consumer socket does not block delivery to other consumers.
exclusiveConsumer
_boolean_
-Enables or disables whether or not queue consumers should be exclusive or not
for example to preserve ordering when not using [Message
Groups](http://activemq.apache.org/Features/Consumer Features/message-groups)
+Enables or disables whether or not queue consumers should be exclusive or not
for example to preserve ordering when not using [Message Groups](message-groups)
nestedMapAndListEnabled
_boolean_
-Enables/disables whether or not Message properties and MapMessage entries
support [Nested Structures](http://activemq.apache.orgFeatures/Message
Features/structured-message-properties-and-mapmessages) of Map and List objects
+Enables/disables whether or not Message properties and MapMessage entries
support [Nested Structures](structured-message-properties-and-mapmessages) of
Map and List objects
objectMessageSerializationDefered
@@ -4766,7 +4766,7 @@ prefetchPolicy
_org.apache.activemq.ActiveMQPrefetchPolicy_
-Sets the [prefetch policy](http://activemq.apache.orgCommunity/FAQ/Using
Apache ActiveMQCommunity/FAQ/Using Apache ActiveMQ/Community/FAQ/Using Apache
ActiveMQ/what-is-the-prefetch-limit-for) for consumers created by this
connection.
+Sets the [prefetch policy](what-is-the-prefetch-limit-for) for consumers
created by this connection.
producerWindowSize
@@ -4804,7 +4804,7 @@ useAsyncSend
_boolean_
-Forces the use of [Async Sends](http://activemq.apache.orgFeatures/Message
Dispatching Features/async-sends) which adds a massive performance boost; but
means that the send() method will return immediately whether the message has
been sent or not which could lead to message loss.
+Forces the use of [Async Sends](async-sends) which adds a massive performance
boost; but means that the send() method will return immediately whether the
message has been sent or not which could lead to message loss.
useBeanNameAsClientIdPrefix
@@ -4832,7 +4832,7 @@ warnAboutUnstartedConnectionTimeout
_long_
-Enables the timeout from a connection creation to when a warning is generated
if the connection is not properly started via {@link Connection#start()} and a
message is received by a consumer. It is a very common gotcha to forget to
[start the
connection](http://activemq.apache.orgCommunity/FAQ/ErrorsCommunity/FAQ/Errors/Community/FAQ/Errors/i-am-not-receiving-any-messages-what-is-wrong)
so this option makes the default case to create a warning if the user forgets.
To disable the warning [...]
+Enables the timeout from a connection creation to when a warning is generated
if the connection is not properly started via {@link Connection#start()} and a
message is received by a consumer. It is a very common gotcha to forget to
[start the connection](i-am-not-receiving-any-messages-what-is-wrong) so this
option makes the default case to create a warning if the user forgets. To
disable the warning just set the value to < 0 (say -1).
watchTopicAdvisories
@@ -4902,7 +4902,7 @@ A [DOT](http://www.graphviz.org/) file creator plugin
which creates a DOT file s
_\<connectionFactory>_
-A [Spring](http://www.springframework.org/) enhanced connection factory which
will automatically use the Spring bean name as the clientIDPrefix property so
that connections created have client IDs related to your Spring.xml file for
easier comprehension from [JMX](http://activemq.apache.orgFeatures/jmx).
+A [Spring](http://www.springframework.org/) enhanced connection factory which
will automatically use the Spring bean name as the clientIDPrefix property so
that connections created have client IDs related to your Spring.xml file for
easier comprehension from [JMX](jmx).
_\<constantPendingMessageLimitStrategy>_
@@ -5039,7 +5039,7 @@ A Flow provides different dispatch policies within the NMR
_\<masterConnector>_
-Connects a Slave Broker to a Master when using [Master
Slave](http://activemq.apache.orgFeatures/ClusteringFeatures/Clustering/Features/Clustering/masterslave)
for High Availability of messages.
+Connects a Slave Broker to a Master when using [Master Slave](masterslave) for
High Availability of messages.
_\<memoryPersistenceAdapter>_
@@ -5049,11 +5049,11 @@ Used to keep track of how much of something is being
used so that a productive w
_\<messageGroupHashBucketFactory>_
-A factory to create instances of {@link SimpleMessageGroupMap} when
implementing the [Message Groups](http://activemq.apache.org/Features/Consumer
Features/message-groups) functionality.
+A factory to create instances of {@link SimpleMessageGroupMap} when
implementing the [Message Groups](message-groups) functionality.
_\<mirroredQueue>_
-Creates [Mirrored Queue](http://activemq.org/siteFeatures/Destination
FeaturesFeatures/Destination Features/Features/Destination
Features/mirrored-queues) using a prefix and postfix to define the topic name
on which to mirror the queue to.
+Creates [Mirrored Queue](mirrored-queues) using a prefix and postfix to define
the topic name on which to mirror the queue to.
_\<multicastNetworkConnector>_
@@ -5153,7 +5153,7 @@ Converts Message from one JMS to another
_\<simpleMessageGroupMapFactory>_
-A factory to create instances of {@link SimpleMessageGroupMap} when
implementing the [Message Groups](http://activemq.apache.org/Features/Consumer
Features/message-groups) functionality.
+A factory to create instances of {@link SimpleMessageGroupMap} when
implementing the [Message Groups](message-groups) functionality.
_\<statements>_
@@ -5215,11 +5215,11 @@ Identify if a limit has been reached
_\<virtualDestinationInterceptor>_
-Implements [Virtual Topics](http://activemq.apache.orgFeatures/Destination
Features/Features/Destination Features/virtual-destinations).
+Implements [Virtual Topics](virtual-destinations).
_\<virtualTopic>_
-Creates [Virtual Topics](http://activemq.org/siteFeatures/Destination
Features/Features/Destination Features/virtual-destinations) using a prefix and
postfix. The virtual destination creates a wildcard that is then used to look
up all active queue subscriptions which match.
+Creates [Virtual Topics](virtual-destinations) using a prefix and postfix. The
virtual destination creates a wildcard that is then used to look up all active
queue subscriptions which match.
_\<vmCursor>_
@@ -5235,5 +5235,5 @@ Pending messages
_\<xaConnectionFactory>_
-A [Spring](http://www.springframework.org/) enhanced XA connection factory
which will automatically use the Spring bean name as the clientIDPrefix
property so that connections created have client IDs related to your Spring.xml
file for easier comprehension from
[JMX](http://activemq.apache.orgFeatures/jmx).
+A [Spring](http://www.springframework.org/) enhanced XA connection factory
which will automatically use the Spring bean name as the clientIDPrefix
property so that connections created have client IDs related to your Spring.xml
file for easier comprehension from [JMX](jmx).
